On Thu, 12 Dec 2002 02:53:24 +0100, J.A. Magallon wrote: > Hi... > > I am getting tons of messages like this on syslog: > > Dec 12 02:01:31 werewolf pam_timestamp_check: pam_timestamp: `/' owner GID > != 0 Dec 12 02:02:06 werewolf last message repeated 7 times Dec 12 > 02:03:11 werewolf last message repeated 13 times Dec 12 02:04:16 werewolf > last message repeated 13 times Dec 12 02:05:21 werewolf last message > repeated 13 times Dec 12 02:06:26 werewolf last message repeated 13 times > Dec 12 02:07:31 werewolf last message repeated 13 times Dec 12 02:08:36 > werewolf last message repeated 13 times ... > > werewolf:~# ls -ld / > drwxr-xr-x 19 root adm 1024 dic 12 01:42 // > > If I chown 0.0 /, when msec is run again by cron, it returns to root.adm. > > /usr/share/msec/perm.3 (my level) reads: > > # Welcome in Level 3 > ### > / root.adm > 755 /bin/ root.root > 755 /bin/ping root.root > 4755 > > Should this be root.root ? Levels 3 and 4 set it to root.adm, rest of > levels to root.root. > > What's happening ? Bug ?
I'll fix the pam timestamp checker to no longer warn with root.adm.. Thanks.. -- Frederic Crozat MandrakeSoft
