Discuss

discuss@lists.centos.org

3 participants
34748 discussions

A bareos question
by m.roth＠5-cent.us 07 Dec '15

07 Dec '15

I've upgraded to 15.2, which has a webui. However, I'd like to tell it to use kerboros, not a hard-coded password in a configuration file. Any clues? mark

1 0

Using typescript as a default shell?
by Benjamin Smith 07 Dec '15

07 Dec '15

Is it possible to use 'script' command that records what happens in a session as the default shell? How could you deal with multiple logins at once? What about output from rsync and the like?

4 4

Centos 7 Yum conflict libicalss
by david 07 Dec '15

07 Dec '15

Folks My Centos 7 systems are all failing to update because of Error: Package: orage-4.10.0-4.el7.x86_64 (@epel) Requires: libicalss.so.0()(64bit) Removing: libical-0.48-6.el7.x86_64 (@base) libicalss.so.0()(64bit) Updated By: libical-1.0.1-1.el7.x86_64 (cr) ~libicalss.so.1()(64bit) Error: Package: orage-4.10.0-4.el7.x86_64 (@epel) Requires: libicalvcal.so.0()(64bit) Removing: libical-0.48-6.el7.x86_64 (@base) libicalvcal.so.0()(64bit) Updated By: libical-1.0.1-1.el7.x86_64 (cr) ~libicalvcal.so.1()(64bit) Error: Package: orage-4.10.0-4.el7.x86_64 (@epel) Requires: libical.so.0()(64bit) Removing: libical-0.48-6.el7.x86_64 (@base) libical.so.0()(64bit) Updated By: libical-1.0.1-1.el7.x86_64 (cr) ~libical.so.1()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Is there something I should (not) be doing? The command was: yum update David

5 5

About CentOS Marks
by Takuya Yamamoto 07 Dec '15

07 Dec '15

Hello https://www.centos.org/legal/trademarks/ According to above, I found following message. ---------------------- Notwithstanding anything to the contrary provided in these Guidelines, the following are examples of unacceptable uses: 1.Use of the CentOS Marks in connection with commercial redistribution of CentOS software ---------------------- I have a question. What means "Use of the CentOS Marks"? For example, While CentOS is booting up, CentOS show the CentOS logo on Full screen. Is it unacceptable? Or acceptable? If commercial redistribution of CentOS software, Developer have to hide this logo? For example, CentOS System is working, user can show the "CentOS" text words on console. Is it unacceptable? Or acceptable? br ----------------------- Yamamoto Takuya

2 1

Centos-7: odd yum output
by Fred Smith 07 Dec '15

07 Dec '15

Hi all! On 7.1 + CR updates, running "yum list installed | grep -y totem" gives this: yum list installed | grep -y totem totem.x86_64 1:3.14.3-5.el7 @cr totem-nautilus.x86_64 1:3.14.3-5.el7 @cr totem-pl-parser.x86_64 3.10.5-1.el7 @cr and "yum list installed | grep -y totem" gives this: yum list available | grep -y totem gnome-python2-totem.x86_64 2.32.0-20.el7.nux nux-dextop totem-devel.x86_64 1:3.14.3-5.el7 cr totem-mozplugin.x86_64 1:3.8.2-5.el7 base totem-mozplugin-vegas.x86_64 1:3.8.2-5.el7 base totem-pl-parser.i686 3.10.5-1.el7 cr totem-pl-parser-devel.i686 3.10.5-1.el7 cr totem-pl-parser-devel.x86_64 3.10.5-1.el7 cr so then, why is it that "yum install totem-mozplugin" gives this? yum install totem-mozplugin Loaded plugins: fastestmirror, langpacks, nvidia Loading mirror speeds from cached hostfile * base: mirrors.lga7.us.voxel.net * elrepo: iad.mirror.rackspace.com * epel: mirrors.mit.edu * extras: mirror.ash.fastserv.com * nux-dextop: mirror.li.nux.ro * updates: centos.chi.host-engine.com Package 1:totem-mozplugin-3.8.2-5.el7.x86_64 is obsoleted by 1:totem-3.14.3-5.el7.x86_64 which is already installed Nothing to do I don't understand, UNLESS it's saying that the totem package now includes the plugin? OK, I can understand that. But looking at the contents of the RPM, it seems to contain only plugins for itself. I'm just upgrading to 7.x, now, and the 6.x box previously had several plugins installed that I can't find, nor even remember where I found 'em. (probably has to do with my age... :[ ) Advice will be appreciated. thanks in advance! Fred -- ------------------------------------------------------------------------------ Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 ----------------------------- The Boulder Pledge -----------------------------

2 1

lunar notation in crontab
by ken 06 Dec '15

06 Dec '15

Crontab offers many refined facilities for Western calendaring, but none for traditional Eastern-- lunar-- designations. So for example, if one wants specify regular occurring events on full moons or on new moons, there is no way to do this. Emacs (a text processor!?) accomplishes this. The math for calculating lunar calendaring is already available; mathematical functions are already available for simple downloading and so would need simply integration into crond. User settings in crontab would make most sense designated in the 'day of month' field with keyword either 'full' or 'new' (abbreviated with 'f' or 'n') prepended to a signed integer number of days (N * 24 hours). I.e., "new+5" would specify '5 days after the new moon'; "full-1" would specify "24 hours prior to the full moon"; "new+0", "new-0" and "new" would all mean the same: "the moment of the new moon". I suppose that alternate syntaxes could be more refined, including hours and minutes before/after new/full, so possibly useful, but then also more complex. Alternate and more refined time periods would be a question for developers.

3 2

Firewalld zone conflict
by Colin Coles 04 Dec '15

04 Dec '15

Hi, In CentOS7 I have added two zones using firewall-cmd, each for different ports/services and interfaces when I try to --add-source to the second zone with an IP that is already in the first I am getting an 'Error: ZONE_CONFLICT' message. Am I trying to do something illogical or is this a feature? Cheers, Colin.

2 2

CentOS 7.2 - no GUI login after upgrade
by Earl A Ramirez 04 Dec '15

04 Dec '15

After installing and enabling the centos-release-cr repo on my CentOS 7.1 laptop; I ran yum clean all and yum update. Yum complained about gstreamer1 dependencies that is caused by epel repo; therefore, I excluded it from the epel repo and run yum update one more time and it went through. After the update was completed I rebooted the laptop and I will just get the splash screen but will never get to the actual login screen; I have experienced this in the past from CentOS 7.0 to 7.1 upgrade and at that time it was caused by SELinux relabeling some of the configuration files; e.g. /etc/passwd and /etc/shadow. This was discovered after I went into single user mode and checked the journal. I booted in the previous successful kernel that loaded and I experienced the same behavior; therefore I went into single user mode from the latest kernel that came with CentOS 7.2 and the previous kernel, checked the journal and there were no errors that give me a hint of what is going wrong. There are no SELinux relabeling but I left the laptop on for a few hours because I was modifying a few directories to accommodate docker and KVM storage from the default setup. Any pointers on how to get the login screen? Thanks in advance. -- Kind Regards Earl Ramirez

4 3

diagnosing noise
by Michael Hennebry 03 Dec '15

03 Dec '15

Though quiet at the moment, my desktop sometimes sometimes makes a noise that I attribute to either a disk or a fan on its last legs. I'm looking for suggestions for distinguishing. For the disk, I expect I should use either hdparm of fsck. Even after reading the man page, I'm not sure how I would use hdparm. If I use fsck, what should I take as evidence of a bad drive? A good drive? Is there a way to tell whether the OS thinks a fan is on? Is there a way to turn a fan on or off manually? Time for a backup. -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

4 3

Re: [CentOS] 7.2 kernel panic on boot
by m.roth＠5-cent.us 03 Dec '15

03 Dec '15

Duncan Brown wrote: > On 03/12/2015 17:00, m.roth(a)5-cent.us wrote: >> Duncan Brown wrote: >>> On 03/12/2015 14:29, Leon Fauster wrote: >>>> Am 03.12.2015 um 15:06 schrieb Duncan Brown <centos2(a)duncb.co.uk>: >>>>> On 03/12/2015 13:54, Jonathan Billings wrote: >>>>>> On Thu, Dec 03, 2015 at 01:44:47PM +0000, Duncan Brown wrote: >>>>>>> The last message before it is "switching to clocksource hpet" >>>>>>> >>>>>>> Then the panic scrolls by >>>>>>> >>>>>>> I've no idea if that counts as later or not >>>>>> It's unlikely to be a panic related to your hardware clock (HPET = High Precision Event Timer), so it's probably when the kernel is touching something else on your system. >>>>>> >>>>>> The content of the panic is really the only thing that can help. >>>>>> >>>>> That's what I figured, but how do I go about getting a copy of it? >>>>> >>>>> Most of it has scrolled by when it's finished >>>> start for example with a photo (or video and grab the frame where the panic occurs) and - disable grub options like rhgb or quit ... >>> Here is a couple of pictures, >> ^^ should be are.* >>> http://i.imgur.com/Vqvqn1H.jpg >>> http://i.imgur.com/WQaz1j9.png >>> >>> Any use? >> I'm just guessing here, but it looks to me as though it's looking at inodes - so filesystem, and kernel modules, maybe video - notice the blacklist. >> >> Wonder if this is a grub2 issue, and it's not finding the filesystem. This isn't, by chance, a secure boot, not BIOS, system? >> > No nothing that exciting, BIOS, and xfs on lvm2. Pretty much the standard options anaconda gives you > > And it boots fine in 3.10.0-229.20.1.el7.x86_64 A thought: did you say you'd rebuilt the ramfs, making sure both xfs and lvm drivers were included? mark

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss