On 09-Jun-05, 03:20 (CDT), "Frode E. Moe" <[EMAIL PROTECTED]> wrote:
> Anyway, now the users cannot edit their own crontabs.
> Here's sample output from "ls -la /var/spool/cron/crontabs":
> drwx-wx--T 2 root crontab 4096 Sep 16 2004 .
> drwxr-xr-x 5 root root 4096 Dec 15 2003 ..
> -rw------- 1 root serverteam 303 Sep 16 2004 serverteam
> (..more files which all are owned by root:users-group..)
Yeah, that's wrong with the new non-suidroot crontab program.
> I manually chown'ed the files to user:crontab, and things are back to
> normal.
Exactly the correct fix.
> I actually remember some "chmod" warnings scrolling by during the
> upgrade, but I cannot remember the specifics.
The cron upgrade should have updated the user/group on the crontabs to
match the new crontab. I'd guess that having NIS shutdown during the
cron upgrade broke this. Likewise, when cron restarted before NIS, there
was no way for it to check userids on the crontabs as it was loading
them (it does more checks now than it did in woody, to prevent various
attacks).
I'm not sure what I can do about this. Cron can't *depend* on NIS,
obviously, and there's no way to tell dpkg *if* NIS is installed, *then*
please configure and start it before doing cron. (I wish someone had
run into this before the Sarge release; at least I could have added
something to the Release Notes. Hmmm, maybe I still can.)
I'm going to leave this open for now, so that others may see it.
Steve
--
Steve Greenland
The irony is that Bill Gates claims to be making a stable operating
system and Linus Torvalds claims to be trying to take over the
world. -- seen on the net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
