On Sat, 2005-03-05 at 22:18, Kevin Krieser wrote:

I had this problem when I tried a generic kernel.org kernel on Suse 9.2.

Should have said I am on SuSE pro 9.1.

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

* Only reply to the list please*

Do you understand why I have this line in my sig? It is because I DON'T need two copies of people's replies to my messages! I get one from the list and that is enough! I don't also need a personal reply. Also please DO NOT top post unless the email client you are using doesn't allow you to edit the replies or you are to lazy to scroll to the part of the message you are replying to. Reply to all for example purposes so that Kevin will get two copies. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge

On Sun, 2005-03-06 at 01:04, Darryl Gregorash wrote:

Ken Schneider wrote:

...

Trying to get xntp to run and end up with the following errors:

5 Mar 17:28:10 ntpd[4451]: cap_set_proc() failed to drop root privileges: Operation not permitted 5 Mar 17:28:13 ntpd[4474]: cap_set_proc() failed to drop root privileges: Operation not permitted 5 Mar 17:55:17 ntpd[7868]: cap_set_proc() failed to drop root privileges: Operation not permitted 5 Mar 17:58:54 ntpd[9515]: cap_set_proc() failed to drop root privileges: Operation not permitted

Over and over. I have the latest update available from YOU. Any suggestions. Tried looking on the archives but found nothing related to this. Even reinstalled from the install DVD with same results. Maybe something in one of the kernel updates.

It's strange that you keep getting different PIDs there. Could you post the results of "head /var/log/" pls (if you're using the "alternate" log)? Also, you aren't running it suid, or chrooted, are you?

It is set to run chrooted. The process starts initially then stops. Runs for less than 1-2 seconds. The configuration in /etc/sysconfig/xntp has the user set to ntp (which does exist). As to the different pid's it is because I kept running rcxntpd start. Yet when I run rcxntpd status it reports that it is dead. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge

On Sunday 06 March 2005 13:21, Ken Schneider wrote:

It is set to run chrooted. The process starts initially then stops. Runs for less than 1-2 seconds. The configuration in /etc/sysconfig/xntp has the user set to ntp (which does exist). As to the different pid's it is because I kept running rcxntpd start. Yet when I run rcxntpd status it reports that it is dead.

You have the dazuko kernel module loaded. It is broken in the sense that it interferes with the kernel capabilities features. This is why xntpd fails, and you also have trouble with vsftpd when you have dazuko loaded. AFAIK there is an update on the way

The Sunday 2005-03-06 at 16:24 -0500, Ken Schneider wrote:

On Sun, 2005-03-06 at 15:42, Anders Johansson wrote:

...

On Sunday 06 March 2005 13:21, Ken Schneider wrote: You have the dazuko kernel module loaded. It is broken in the sense that it interferes with the kernel capabilities features. This is why xntpd fails, and you also have trouble with vsftpd when you have dazuko loaded. AFAIK there is an update on the way

It never ceases to amaze me as to how Anders has the answer.

Another dazuko related problem was mentioned in suse-security recently. I'd guess he has been investigating about dazuko ;-) -- Cheers, Carlos Robinson