On Thu, Jan 02, 2003 at 11:37:27PM +0100, Richard Bos wrote:
Do you happen to be remote?
I do... And just for the record: this is 8.1
What happens if you change the editor to e.g. joe, like;
$EDITOR was unset. Setting it (e.g. export EDITOR=vim) doesn't help.
(I don't expect this to be solution as you've problems with crontab -l as well)
Indeed: jon@Scum:~> crontab -e -bash: /usr/bin/crontab: Permission denied jon@Scum:~> crontab -l -bash: /usr/bin/crontab: Permission denied jon@Scum:~> which crontab /usr/bin/crontab jon@Scum:~> ll /usr/bin/crontab -rwsr-x--- 1 root trusted 22632 Sep 9 21:05 /usr/bin/crontab Hmmm: Scum:/home/jon # find / -group trusted -ls 24832 36 -rwsr-x--- 1 root trusted 35064 Sep 9 21:56 /usr/bin/at 25316 24 -rwsr-x--- 1 root trusted 22632 Sep 9 21:05 /usr/bin/crontab 24569 36 -rwsr-x--- 1 root trusted 35320 Sep 10 21:13 /usr/bin/gpasswd A small community, eh? I suppose adding my user 'jon' to the 'trusted' group might work, but I also kind of think it might be ...well not "The Right Thing" to do?
Op donderdag 2 januari 2003 23:33, schreef Jonathan Nichols:
I created both /etc/cron.allow and /etc/cron.d/allow as I'd do on a Solaris box and added my own username to the file, and kill -HUP'd cron.
jon@Scum:~> man 1 crontab talks of: FILES /var/spool/cron/allow /var/spool/cron/deny but creating the 'allow' file, adding jon to it, and subsequently restarting cron doesn't seem to have any effect either... I think it's a permissions issue, but I'm not sure how to fix it...? It *would* be nice to not have to 'su' in order to change my cronjobs... *Should* I add 'jon' to 'trusted' ...? (I *do* ...sort of... trust myself ;) TIA Jon Clausen