Sponsored Content
Operating Systems Linux Red Hat /usr/sbin/crond: can't lock /var/run/crond.pid, Post 302465404 by verdepollo on Friday 22nd of October 2010 10:39:26 AM
Old 10-22-2010
Is there any relevant info in cron log?

Perhaps it's not an issue with the daemon itself but with the line you put in your crontab?

Last edited by verdepollo; 10-22-2010 at 11:58 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/usr/sbin/getty

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 - Please help

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

crond

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

syslog: /usr/sbin/envd[1075]:

hi friends, what is the meaning of this error ? syslog: /usr/sbin/envd: (2 Replies)
Discussion started by: cromohawk
2 Replies

5. Solaris

crontab /usr/sbin/rtc log rc=1

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

redhat 5.2 tikanga crond running but not reading crontab file

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

crond not work after writing to cron log?

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

Testing privileges -lock lockfile /var/lock/subsys/..- Permission denied

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

crond: Authentication token is no longer valid; new one required.

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

Alternative for /usr/sbin/userdbset on Linux

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
CRONTAB(1)						      General Commands Manual							CRONTAB(1)

NAME
crontab - maintain crontab files for individual users (V3) SYNOPSIS
crontab [ -u user ] file crontab [ -u user ] { -l | -r | -e } DESCRIPTION
Crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have their own crontab, and though these are files in /var, they are not intended to be edited directly. If the allow file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but the deny file does exist, then you must not be listed in the deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to use this command. 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(8) can confuse crontab and that if you are running inside of su(8) 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. SEE ALSO
crontab(5), cron(8) FILES
/etc/cron.allow /etc/cron.deny STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax. DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line. AUTHOR
Paul Vixie <paul@vix.com> 4th Berkeley Distribution 29 December 1993 CRONTAB(1)
All times are GMT -4. The time now is 07:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy