Sponsored Content
Full Discussion: Unable to update the Crontab
Operating Systems Solaris Unable to update the Crontab Post 302107910 by ONEX on Wednesday 21st of February 2007 03:18:15 PM
Old 02-21-2007
Does the crontab time stamp change again to the time of the 2nd login? Is there something in roots .login or .profile that rewrites the crontab from another location?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Pro*C Update not working from Crontab

Dear All, I have writen a Pro*c program that does a data base select,insert,update statements and I have scheduled the program to run from crontab, It is runing fine for the select insert and commit statement till it reaches the update statement , it throws the following error: SQL On IPB... (2 Replies)
Discussion started by: alhallay
2 Replies

2. Fedora

Unable to Update Date

Hi everyone, Thanks for your help with this. I'm running an AWS EC2 instance (ami-2bc05345) and the time has been drifting. I have a different server using the same instance where the time is fine. NTP seems to be installed and be running (I uninstalled it and reinstalled it via Yum, just to... (4 Replies)
Discussion started by: AaronLS2
4 Replies

3. Solaris

Unable to open Crontab

Hi, I have 2 solaris server. I can able to open to see cron entry by using crontab -l in one of the server. I cant able to open another server. How to check if crontab is fixed in that server. If not then how to make a crontab in that server. Please advice. Thanks, Mani ----------... (1 Reply)
Discussion started by: Mani_apr08
1 Replies

4. UNIX for Dummies Questions & Answers

UNABLE TO UPDATE! HELP!

I just installed the latest version of ubuntu and I can't run the update manager without getting an error message. Im not sure what info i need to post so i can get help so just tell me if i need to post info because i would like to use ubuntu. (2 Replies)
Discussion started by: Brandyn
2 Replies

5. Linux

Unable to update Fedora after upgrading from Fedora17 to Fedora18

I have just upgraded to fedora 18 from 17 using fedup tool. The upgradation process succeeded and I can feel the new desktop appearance of fedora18. when I tried to update using yum update. I can see that the fedora17 files are not removed completely and they are also listed below the files to... (1 Reply)
Discussion started by: vaibhavvsk
1 Replies

6. UNIX for Dummies Questions & Answers

Unable to invoke mercurial client from crontab

We have the Mercurial client installed on our linux machine. $ hg --version Mercurial Distributed SCM (version 2.2.3)When I try to invoke it using a cronjob, it fails with the message "command not found". $ crontab -l # DO NOT EDIT THIS FILE - edit the master and reinstall. #... (2 Replies)
Discussion started by: balajesuri
2 Replies

7. Red Hat

Unable to perform yum update

Hi, I run RHEL 5.2 as a server in my lab. Now the issue I am facing is that I am unable to update my machine using yum update. It shows an error of missing dependencies though dependencies are already installed. Please help me to do that. Error screen shot is also attached. (9 Replies)
Discussion started by: Ankur Goyal
9 Replies

8. Linux

Unable to update package.

I am trying to update an openssl package on my node. # yum update openssl-1.0.1e-60.el7.x86_64 Loaded plugins: product-id, rhnplugin, subscription-manager This system is receiving updates from RHN Classic or Red Hat Satellite. baseline_prd_channel ... (0 Replies)
Discussion started by: Junaid Subhani
0 Replies

9. Shell Programming and Scripting

Crontab update

Hello. We have a big crontab file where we need to comment out for few countries and also uncomment out based on situations . Could someone let us know how this can be done using a script . Sample file look like & here i need to comment/uncomment based on country code . 0-59 ...... (15 Replies)
Discussion started by: ron5174
15 Replies
CRONTAB(1)						    BSD 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
The crontab utility 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. The format of these files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for comments. 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 following options are available: -u Specify 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. -l Display the current crontab on standard output. -r Remove the current crontab. -e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified crontab will be installed automatically. FILES
/var/cron/allow List of users allowed to use crontab /var/cron/deny List of users prohibited from using crontab /var/cron/tabs Directory for personal crontab files 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'') with the exception that the dangerous variant of calling crontab without a file name in the first form of the command is not allowed by this implementation. The pseudo-filename '-' must be specified to read from standard input. The new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax. AUTHORS
Paul Vixie <paul@vix.com> BSD
May 13, 2010 BSD
All times are GMT -4. The time now is 08:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy