12-08-2010
Cron on Solaris not editing.
I am working on Solaris machine.
I have to add a cron for some operation, nut in SSH terminal crontab -l shows all related crons, but crontab -e instead of opening vi editor shows some number.
Could any body tell what can be issue?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Firstly, thank you for this great forum and the time you spend on answering newbies like me.
I still have a problem with understanding how profiling works on a solaris 2.6 unix system.
when adding a user, it should get a profile in /home I suppose.
And again, I suppose that this is the file... (7 Replies)
Discussion started by: phpote
7 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am accessing CRON via telnet and want to set up some jobs. I have typed crontab -e to edit my cronfile but I can't seem to enter anything when I type on my keyboard. All I have is a flashing cursor at the top with ~ on the start of each line.
How can I enter the jobs and save this... (9 Replies)
Discussion started by: jaffy1229
9 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Im just begining in UNIX and i want to know how to create a CRON schedule to take a file, compact it and copy it by ftp to other computer running Linux.
Thanks alot folks!
Macakongs2099 (2 Replies)
Discussion started by: Macakongs2099
2 Replies
4. Solaris
im running crontab -e as root, I keep getting, I set my editor to EDITOR=vi...
# crontab -e
477 (2 Replies)
Discussion started by: csaunders
2 Replies
5. Solaris
I have a script that needs to install a script the runs just before cron starts. Currently (for 9 and older), it simply finds the name of the cron script in /etc/rc?.d, decrements the number and creates a link.
For example, if cron starts with /etc/rc2.d/S75cron, the install script extracts the... (3 Replies)
Discussion started by: BOFH
3 Replies
6. UNIX for Dummies Questions & Answers
I want to set up a file with crontab to run the cron deamon so I can use at to schedule jobs. I think the crontab file (or whatever you call it) has to be set up. Currently, I don't have a crontab file (I checked by typing sudo crontab -u myusername -l), and I don't know the syntax for creating... (6 Replies)
Discussion started by: Ultrix
6 Replies
7. Solaris
I am interested in doing some heavy video work. I have a ADVC 110 Video capture device, which I am using to capture VHS video tapes, which I will convert on the server to DVD format and burn to DVD's using DVD production software. I will also take the captured video file and split it up in parts... (1 Reply)
Discussion started by: Marcus Aurelius
1 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I am running a script thorugh cron which is given below.
this script is not doing its defined job through cron ,files are still in unzipped state.
But when i run this script as ./script.sh it gets executed fine and does all that is required.
also when i run thi script as sh... (2 Replies)
Discussion started by: Jcpratap
2 Replies
9. UNIX for Dummies Questions & Answers
I have a (stupid) question about cron. If 'cd' is used in cron script, do we have to 'cd' back to 'starting' dir at the end of script (for other scripts and programs to work)? (1 Reply)
Discussion started by: orange47
1 Replies
10. Shell Programming and Scripting
Dear Guru's
I'm using Putty and want to edit a file. I know we generally use vi editor to do it. As I'm not good in using vi editor, I want to convert the vi into something like text pad. Is there any option in Putty to do the same ? Thanks for your response.
Srini (6 Replies)
Discussion started by: thummi9090
6 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