08-22-2007
Nope! sorry that doesnt work
crontab -e jravisha
crontab: usage error: no arguments permitted after this option
usage: crontab [-u user] file
crontab [-u user] [ -e | -l | -r ]
(default operation is replace, per 1003.2)
-e (edit user's crontab)
-l (list user's crontab)
-r (delete user's crontab)
-i (prompt before deleting user's crontab)
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error
jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c
gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
Discussion started by: handak9
2 Replies
2. Shell Programming and Scripting
Plz advise on the following error for a crontab job i have scheduled for running a script
/usr/lib/dld.sl: Can't open shared library: /home/build3p/PMReleases/Symphony711/HP-UX/rw/710/lib/libtls4d.sl
/usr/lib/dld.sl: No such file or directory
/ushhquest/data001/Scripts/Inform/Build_Data.sh:... (0 Replies)
Discussion started by: reader_regular
0 Replies
3. UNIX for Advanced & Expert Users
Hi,
I'm using WRQ Reflections 12.0.6 on Windows XP to open a Xsession to HP 11.11 server. After providing password, the CDE window is displayed and then receive a "dtdbcache failure" message "Couldn't recreate the Desktop Actions/Datatypes Database. Check disk space and/or permissions." I... (3 Replies)
Discussion started by: Leese
3 Replies
4. UNIX for Advanced & Expert Users
Hi all,
I am using Perl program to do socket communication. My application has to use port 40001 this is a condition I can't change the port.
The execution of this script always gave an error 'Bind failure port already in use'
netstat execution gives below line:
udp 0 0 ... (5 Replies)
Discussion started by: zing_foru
5 Replies
5. UNIX for Advanced & Expert Users
Usually when su rejects an attempt to switch user it responds with "Sorry" but with a certain username on some unix servers the response is "Killed". I'm guessing the su accepted the username/password but refused to spawn child shell with the specified username. What's causing this and what has to... (8 Replies)
Discussion started by: twk
8 Replies
6. Solaris
Our Solaris was hung yesterday, and dmesg show that,
nxge3 : <== nxge_m_start: initialization failed
nxge2 : nxge_dma_mem_alloc:ddi_dma_mem_alloc kmem alloc failed
nxge2 : nxge_alloc_rx_buf_dma: Alloc Failed: dma 9 size_index 10 size requested 4194304
Does it mean the DMA failure ? How... (5 Replies)
Discussion started by: dehetoxic
5 Replies
7. Shell Programming and Scripting
Hello,
Sometimes when i execute my shell that makes sftp it gives me this error:
Couldn't close file: Failure.
What does it mean?, how can i make sure it will do ok?.
Bye (2 Replies)
Discussion started by: rubber08
2 Replies
8. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
9. Solaris
Hi Team,
Am new to solaris. There is a script in the crontab that issues backup at a scheduled time. It fails alway. here are some logs. Can anyone please help why backup fails.:
sdpuser@sdp3a>dmesg ... (4 Replies)
Discussion started by: andersonedouard
4 Replies
10. UNIX for Advanced & Expert Users
Dear all,
I noticed in syslog that i receive authentication failure from cron:
Mar 11 23:19:01 s1 CRON28789]: Authentication failure
Mar 11 23:19:01 s1 cron: Authentication failure
Mar 11 23:19:01 s1 cron: Authentication failure
Mar 11 23:19:01 s1 CRON: Authentication failure
Mar 11... (3 Replies)
Discussion started by: mydove
3 Replies
LEARN ABOUT FREEBSD
crontab
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