08-27-2008
Checking environment
How do you know you have the same environment. Perhaps it would be useful to put this in your crontab for a minute or so:
* * * * * printenv|sort
When you get the email, compare it to your own command-line version.
10 More Discussions You Might Find Interesting
1. Solaris
I have a simple backup script that I am running to back up drives across the network. However I need to have detailed log files for this script such as time backup started, what was backed up, if there were any errors and the time that the backup was complete. I would also like the script to... (3 Replies)
Discussion started by: valicon
3 Replies
2. Shell Programming and Scripting
Hi,
I have a query. When I execute a shell script say sh1.ksh,
at the run time I need to put another shell script say sh2.ksh
in the crontab with the parameter which we provided to sh1.ksh
script, to execute sh2.ksh on the background for doing process.
Also the cron entry needs to be... (1 Reply)
Discussion started by: mrpranab
1 Replies
3. Shell Programming and Scripting
I would like to write a script that would create 1000 files like clm0001.txt to clm1000.txt. All the files would contain the same contents. How do I achieve this using a script?Please help. (2 Replies)
Discussion started by: ggayathri
2 Replies
4. Shell Programming and Scripting
I am trying to FTP files to a Windows server through my Linux machine. I have setup the file transfer with no problems but am having problem deleting those files from the Linux box. My current non-working solution is below. Any ideas, anyone?? :wall: Please be gentle, I'm fairly new to this... (4 Replies)
Discussion started by: jmalfhs
4 Replies
5. Shell Programming and Scripting
Hi,
I developed one shell script where it will sync the files using perforce,
#!/bin/bash
TERM=linux
export TERM
clear
echo ""
$PATH
echo ""
cd /u/userk/p4/p4_client/TES_DATE
echo ""
echo "Sync p4 "
p4 sync
echo "Executing for second time "
p4 -u userk -p p4net:161 -c... (8 Replies)
Discussion started by: asak
8 Replies
6. Shell Programming and Scripting
while running the following code in ssh crontab, Its running successfully
but its not creating text file IFC1.txt, file1.txt, file2.txt
while running manually its working.
please help me
#!/bin/ksh
hostname > file1.txt 2>/dev/null
hostname >> file1.txt 2>/dev/null
sudo df -h | grep... (2 Replies)
Discussion started by: elango963
2 Replies
7. UNIX for Dummies Questions & Answers
I have a script file (fmlist.sh), i need the output of this script to write to a logfile (Mod_Alm_log.txt). If i execute the below manually it works, but when using in crontab the file is empty.
cd /home/dreid12/als/Modernization && ./fmlist.sh > Mod_Alm_log.txt
Any ideas? This is unix on a... (1 Reply)
Discussion started by: mytouchsr
1 Replies
8. Shell Programming and Scripting
Hi,
I am creating a shell script which will check the processing of the main script if the error count is more than 2% of the record count in a feed. Part of the code is below:
err_tol=`echo $feed_cnt \* 0.02 |bc`
while read line
do
err_cnt=$(grep -i "$line" $err_log | wc -l)
... (5 Replies)
Discussion started by: member2014
5 Replies
9. UNIX for Advanced & Expert Users
Hi
I am new to Linux / scripting language. I need to improve our Linux servers at work and looking to claim some space my deleting log files/ folders on a 5 day basis.
Can someone help me with creating a script to do so.
Any sample script will be helpful.:b:
Regards (2 Replies)
Discussion started by: sachinksl
2 Replies
10. Shell Programming and Scripting
I've got this script to loop through all folders and move files that are more than 2 years old. I'm using the install command because it creates the necessary directories on the destination path and then I remove the source. I'd like to change the script to use the mv command since it is much... (4 Replies)
Discussion started by: consultant
4 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 they are not intended to be edited directly.
(Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.)
If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the
/usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
/usr/lib/cron/cron.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 com-
ments.
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
/usr/lib/cron/cron.allow
/usr/lib/cron/cron.deny
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). 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
December 29, 1993 BSD