10-22-2010
have a look at cron.allow and cron.deny files (location may depends on OS) make sure your user is allowed
check autorisation and ownership of /var/run/ tree ensure the user running the crond can write in it
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How can i restart the console getty without rebooting the system on HPUX 11.0
Normally it will be stated by ps -ef | grep getty
console 0:00 /usr/sbin/getty console console
many thanx (4 Replies)
Discussion started by: iceman_denmark
4 Replies
2. Solaris
WARNING - /usr/sbin/fsck not found. Most likely the mount of
/usr failed or the /usr filesystem is badly
damaged. The system is being halted.
Either re-install the system of boot with -b
option in an attempt to recover
Anyone help me on restoring this without having to reinstall. it is a... (8 Replies)
Discussion started by: frustrated1
8 Replies
3. UNIX for Dummies Questions & Answers
I noticed that I do not have the crond daemon in my AIX box. I need to create a backup script to run nightly. Where do I find this daemon?
Thanks (1 Reply)
Discussion started by: dkbainbridge
1 Replies
4. HP-UX
hi friends,
what is the meaning of this error ?
syslog: /usr/sbin/envd: (2 Replies)
Discussion started by: cromohawk
2 Replies
5. Solaris
I noticed in my cron log file for my solaris 8 servers the rc=1. I imagine that is return code and something did not process. Does anyone know what that is, is there fix or the implications of leaving it?
Thank you
> CMD: && /usr/sbin/rtc -c > /dev/null 2>&1
> root 22049 c Fri Dec 19... (1 Reply)
Discussion started by: csgonan
1 Replies
6. Red Hat
Issue:crond is running, can even restart it and /var/log/cron shows it starting. The /etc/crontab file is correct as compared to another machine. I set the crontab file to enter a datestamp into a file under /tmp every minute. Thing is, the crontab file is not being read or cron is not working... (12 Replies)
Discussion started by: robjmarquez
12 Replies
7. UNIX for Dummies Questions & Answers
Yesterday I was testing out some cron commands and when i was check the /var/log/cron with vi editor I accidentally did :wq instead. Since then the log has not updated and I'm assuming no cronjob is running because looking at the log there's activities everyday
there's some default stuff that... (5 Replies)
Discussion started by: orionoreo
5 Replies
8. UNIX for Advanced & Expert Users
Hi all,
I have to test some user priviliges. The goal is to be sure that an unauthorized user can't restart some modules (ssh, mysql etc...).
I'm trying to automate it with a shell script but in same cases I got the syslog broadcast message.
Is there any way to simply get a return code... (3 Replies)
Discussion started by: Dedalus
3 Replies
9. UNIX for Advanced & Expert Users
Hi can any one please help me
with this
there are some cron jobs running on one of production servers i noticed the jobs are not running for long time, when i checked the logs i founf this message,
information form the server
# chage -l root
Minimum: 0
Maximum: 99999... (2 Replies)
Discussion started by: robo
2 Replies
10. Shell Programming and Scripting
Hello.
I am currently on HPUX and migrating to Linux RHEL 6.4
This program on hpux:
/usr/sbin/userdbset
is puzzling me on linux.
Does anyone know the equivilent program forked or used on linux.
This program is mentioned in our user reset script.
here is a strings of the... (2 Replies)
Discussion started by: olyanderson
2 Replies
LEARN ABOUT NETBSD
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (ISC Cron V4.1)
SYNOPSIS
crontab [-u user]
crontab [-elr]
DESCRIPTION
crontab is the program used to install, deinstall, or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have their
own crontab, and though these are files in /var/cron, they are not intended to be edited directly.
If the /var/cron/allow file exists, then you must be listed therein in order to be allowed to use this command. If the /var/cron/allow file
does not exist but the /var/cron/deny file does exist, then you must not be listed in the /var/cron/deny file in order to use this command.
If neither of these files exists, depending on the compiled in settings, only the super user will be allowed to use this command, or everyone
will be allowed to use this command. On NetBSD everyone is allowed to use this command.
The default maximum size for a crontab is 256 kilobytes, but this may be changed for all users on the system by putting the desired maximum
size (in bytes) in the /var/cron/maxtabsize file.
If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines
``your'' crontab, i.e., the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running
inside of su(1) you should always use the -u option for safety's sake.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is given.
The -l option causes the current crontab to be displayed on standard output.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically.
FILES
/var/cron/allow Optional list of users that are allowed to use crontab.
/var/cron/deny Optional list of users that are disallowed to use crontab.
/var/cron/maxtabsize Maximum size of crontab files. Defaults to 256 kilobytes.
/var/cron/tabs/ Directory containing the individual user crontab files, named after the user.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), cron(8)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). This new command syntax differs from previous versions of Vixie Cron, as well
as from the classic Version 3 AT&T UNIX syntax.
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
May 6, 2010 BSD