Hi,

I am trying to run a cronjob. But while doing so I am getting the following error message :-

can't open yourfile in /var/spool/cron/crontabs directory.
No such file or directory

Well the error messgae suggests it is not there...
Did you look inside /var/spool/cron/crontabs directory?

How did you load your job scheduling?

hi,

Thanks for prompt reply !

When I am trying to access the path. The below message is shown :-

 
ABC@XXX:/var/spool/cron# cd crontabs
ksh: crontabs: permission denied

/var/spool/cron/crontabs is often only accessible to root but not always :

zra:/var/spool/cron $ ll
total 8
dr-xr-xr-x   5 bin        bin           1024 Oct  4  2011 .
dr-xr-xr-x  15 bin        bin           1024 Jun 11  2002 ..
dr-xr-xr-x   2 bin        bin             96 Oct  4  2011 atjobs
-r--r--r--   1 bin        bin            342 Nov  7  1997 crontab.root
dr-xr-xr-x   2 bin        bin             96 Nov 24  2010 crontabs
drwxrwxrwt   2 root       sys           1024 Jul 11 20:20 tmp

crontab -e

I tried using the ABC to get the details using :-

ABC@XXX:/var/spool/cron# ls -l
total 0
drwxrwx---    2 bin      cron            256 Jan 19 11:31 atjobs
drwxrwx---    2 bin      cron            256 Jul 10 16:24 crontabs

root@XXX:/var/spool/cron/crontabs# ls -l
total 56
-rw-r--r--    1 adm      cron           2020 Feb 28 2007  adm
-rw-------    1 root     cron            222 Jan 22 2008  hostmon
-rw-------    1 root     cron            225 Jul  9 15:15 root
-rw-------    1 root     cron             85 Jun 22 15:11 root-5JULLY2012
-rw-r--r--    1 sys      cron            853 Feb 28 2007  sys
-rw-------    1 root     cron            199 Jul 10 16:24 tcadm
-rw-r--r--    1 root     cron           1122 Feb 28 2007  uucp

root@XXX: /PPP/TRY/pXX/ACV/XXX/XXX /logs# crontab -l
14 15 22 6 5 /PPP/TRY/pXX/ACV/XXX/XXX/XXX/CronScriptCheck/Script.ksh
20 15 * * *  /PPP/TRY/pXX/ACV/XXX/XXX/XXX/CronScriptCheck/ AScript.ksh 

If you have root account, then add your user in cron.allow (in /var/adm/cron/ directory) if cron. allow does not exist nor cron.deny (or cron.deny empty...), then anybody can use cron...

The best is to have a cronfile per user / product admin, but then you have no idea what is scheduled unless you read all the files... One is the best for reading and to see for performance issues /contention etc but then on that (root?) person can modify/change... Not suitable in production environments where DBAs are not going to let anyone touch what they plan nor sysadmin, and so you find a few operators with production job scheduling

Here is from a aix (6.1) box:

n12:/home/vbe $ ll /var/adm/cron
total 116520
dr-xr-x---    2 bin      cron            256 Apr 30 2009  .
drwxrwxr-x   14 root     adm            4096 Jul 11 2011  ..
prw-------    1 root     cron              0 Jul 12 16:15 FIFO
-rw-r-----    1 bin      cron              4 Apr 30 2009  at.deny
-rw-r-----    1 bin      cron              3 Apr 30 2009  cron.deny
-rw-rw-r--    1 bin      bin        59620574 Jul 12 16:55 log
-rw-r--r--    1 root     sys            1313 Apr 30 2009  queuedefs