Hi folks,
I've just installed cron and wanted to edit an user's crontab
with crontab -e. This didn't work: permission denied.
It is easy to fix, by chmod ugo+s, but after an update,
the shit starts again ...
Smells like a bug.
cu
--
On Wednesday 21 June 2006 13:34, Enrico Weigelt wrote:
Hi folks,
I've just installed cron and wanted to edit an user's crontab
with crontab -e. This didn't work: permission denied.
It is easy to fix, by chmod ugo+s, but after an update,
the shit starts again ...
Smells like a bug.
More
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Enrico Weigelt wrote:
I've just installed cron and wanted to edit an user's crontab
with crontab -e. This didn't work: permission denied.
Remember that the user must be in the cron group to be able to use cron/crontab.
- --
Arturo Buanzo Busleiman
Enrico Weigelt wrote:
Hi folks,
I've just installed cron and wanted to edit an user's crontab
with crontab -e. This didn't work: permission denied.
Correct.
It is easy to fix, by chmod ugo+s, but after an update,
the shit starts again ...
No, that's not a fix. That's a break in.
Am Mittwoch, 21. Juni 2006 13:34 schrieb ext Enrico Weigelt:
I've just installed cron and wanted to edit an user's crontab
with crontab -e. This didn't work: permission denied.
Looks quite normal.
It is easy to fix, by chmod ugo+s, but after an update,
the shit starts again ...
Or by
It's a dangerous action to change a program's setuid bit!
--
Shaochun Wang(王绍春) [EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list
Dirk Heinrichs wrote:
Am Mittwoch, 21. Juni 2006 13:34 schrieb ext Enrico Weigelt:
It is easy to fix, by chmod ugo+s, but after an update,
the shit starts again ...
Or by editing /etc/cron.allow
Nah, doesn't help. Just have a look at /usr/bin/crontab.
Smells like a bug.
Works as
Hi folks,
Putting the users into the cron group fixed it.
Okay, as it should be ;-o
In all these years I never had a system which required this.
For security reasons, this is not bad, so certain users can be
both allowed to have an crontab but forbidden to edit it.
But this is quite
Am Mittwoch, 21. Juni 2006 14:29 schrieb ext Alexander Skwar:
Or by editing /etc/cron.allow
Nah, doesn't help. Just have a look at /usr/bin/crontab.
Yes, you're right.
Bye...
Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211
On Wed, 21 Jun 2006 15:32:31 +0200, Enrico Weigelt wrote:
But this is quite inconvenient, if you have dozens of users and
want to allow them all to edit their crontabs.
egrep ^.*?:.*?:.*?:100: /etc/passwd | cut -d: -f1 | while read u do gpasswd -a
$u cron; done
will add all users from group
On Wednesday 21 June 2006 16:20, Neil Bothwick wrote:
egrep ^.*?:.*?:.*?:100: /etc/passwd | cut -d: -f1 | while read u do gpasswd
-a $u cron; done
will add all users from group GID 100 (users on this system) to the cron
group.
Well...
awk -F: \$4~/^\
`awk -F: '$1~/^users$/{print $3}'
Enrico Weigelt wrote:
But this is quite inconvenient, if you have dozens of users and
want to allow them all to edit their crontabs.
Why is that inconvenient? Just put them in the appropriate
group - where's the problem?
Alexander Skwar
--
Being a miner, as soon as you're too old and tired
12 matches
Mail list logo
