HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
cancel
Showing results for 
Search instead for 
Did you mean: 

crontab

 
SOLVED
Go to solution
Paul Bertino
Frequent Advisor

crontab

I have setupa user in cron.allow and there is nor cron.deny. Still not auth to use crontab -e
14 REPLIES
James R. Ferguson
Acclaimed Contributor

Re: crontab

Hi Paul:

What error do you get when you do this?

Doing 'crontab -e' invokes an editor ('vi') against a temporary file in '/var/tmp' to build your crontab file if there is none to edit.

Regards!

...JRF...
Paul Bertino
Frequent Advisor

Re: crontab

crontab: you are not authorized to use cron. Sorry.
test01@hellcat:/home/test01>

rleon
Regular Advisor

Re: crontab

to user id has to be in /var/adm/cron/cron.allow
Paul Bertino
Frequent Advisor

Re: crontab

The user id is in the cron.allow.

Re: crontab

>The user id is in the cron.allow.

I tried adding trailing spaces and crontab still worked.
We would need to see more info:
id
vis /var/adm/cron/cron.allow
Robert-Jan Goossens_1
Honored Contributor

Re: crontab

try bouncing the cron daemon.

# /sbin/init.d/cron stop
# /sbin/init.d/cron start

# su - test01
# crontab -e

Regards,
Robert-Jan
Jeff_Traigle
Honored Contributor

Re: crontab

Also make sure the permissions on /usr/bin/crontab have not been altered. I've run into this error on SLES 10 when Bastille removed world read and execute.

-r-sr-xr-x 1 root bin 79468 Feb 15 2007 /usr/bin/crontab
--
Jeff Traigle
Paul Bertino
Frequent Advisor

Re: crontab

Thanks for your help. I still have the issue and I have tried everything you all have suggested.
T G Manikandan
Honored Contributor

Re: crontab

You say you dont have cron.deny file, Can you also remove cron.allow file and try.

Thanks.
Paul Bertino
Frequent Advisor

Re: crontab

I have deleted the cron.allow. Tried the test user test01, no luck. Thanks
T G Manikandan
Honored Contributor
Solution

Re: crontab

can you check if that user exists with /etc/passwd file

cat /etc/passwd|grep
and also check if there are any duplicate UID in the file.

Also try,

creating a crontab file for the user and try
/var/spool/cron/crontabs/ with the file owner as test01.
T G Manikandan
Honored Contributor

Re: crontab

which are your cron.allow and cron.deny files located?
Paul Bertino
Frequent Advisor

Re: crontab

Well, the real cron.allow stand up. There are two locations on our system,
/var/spool/cron
and
/var/adm/cron = this is the correct one!

Sorry for the confusion and thanks to all of you for your help! It does work now!
Paul Bertino
Frequent Advisor

Re: crontab

Thanks. I have the answer and it is working.