It writes the following to the file called cronjob.txt
I added GMT because I do not know your timezone, and I ran this on cycwin - my network connection to my solaris boxes is not available so the output of df -h does not look right
Code:
.cron job run on. Tue Jun 12 21:05:28 GMT 2012
Filesystem Size Used Avail Use% Mounted on
C:/cygwin/bin 452G 69G 384G 16% /usr/bin
C:/cygwin/lib 452G 69G 384G 16% /usr/lib
C:/cygwin 452G 69G 384G 16% /
C: 452G 69G 384G 16% /cygdrive/c
D: 14G 12G 1.6G 89% /cygdrive/d
The echo statement makes line 1. > means open a file, and start writing from the beginning, overwriting the existing stuff in the file. The rest of the file comes from the df -h >> command. The >> means append to the file.
cronjob.txt lives in the login directory for the user whose crontab this came from.
This User Gave Thanks to jim mcnamara For This Post:
I have the following script
awk '$1 ~ /^*+/ {
s += $NF;
m++
}
END {
print NR, m, s
}
and I use it to get results from the following file
A4792 4
COMP9021 5
K9 7
ABC 8
924 1
R2D2 3 (8 Replies)
I have a script that has defined a log file like this.
The name of the script is verify.sh
Inside the script there is some thing like this.
LOG=/usr/verify
TDATE=`date "+%m%d%y"$$`
LOGFILE=$LOG.$TDATE.
and inside the script it has been written as
echo "This is to verify" | tee -a... (2 Replies)
Hi
All,
Can anybody explain what this script is doing?
#!/bin/sh
who | cut -d " " -f1 | sort -u > userlist1
while true ; do
sleep 60
who | cut -d" " -f1 | sort -u >userlist2
for username in `cat userlist1` ; do
if ! grep "^$username$" userlist2 > /dev/null ; then
echo... (0 Replies)
Guys,
was wondering what the meaning of the below bit is ?
awk -F ' ' '{print $1 " " $2 ;}' $TEMPFILE | (rm -f $TEMPFILE; sed 's/$/ '"$box"'/g' > $TEMPFILE)
Can anyone explain this in detail? what is the significance of rm -f $TEMPFILE here? What all IO/buffering happens here ?How the... (0 Replies)
Hello,
I have seen this script on this site. I understand most of it. However I am a bit stuck on the part in red. It appears to be expanding
for file in *.zip
do
zipdir=${file%.*}
mkdir $zipdir || echo "unable to create $zipdir"
cp $file $zipdir || echo "unable to copy $file"... (3 Replies)
#script
fileused=test.txt
hostname=test.dis.com
ftp $hostname <<-! > $fileused.err 2>&1
put file.txt /usr/text.txt
bye
!
kindly the above script the one marked as Bold and underlined as the above i am declaring the new variable as filename ,But when i used i had used as $fileused.err... (1 Reply)
The following script will create a directory in a directory and will go on as many times as the number you will give in.
I am trying to find out how it works ... can someone please help me with that?
#!/bin/sh
#create a variable and set it to 1
n=1
#start a loop as... (3 Replies)
To merge mutiple *.tab files as:
file1.tab
rs1 A A
rs2 A A
rs3 C C
rs4 C Cfile2.ind
rs1 T T
rs2 T T
rs3 G G
rs4 G Gand file3.tab
rs1 B B
rs2 B B
rs3 L L
rs4 L LOutput:
file1.tab file2.tab file3.tab
AA TT BB
AA TT BB
CC GG LL
CC GG ... (4 Replies)
Hi
My friend wrote this particular script and won't tell me what it does, and when I run it I don't understand it.
What does the entire script do with specifics please.
Thanks
Bob
#!/bin/bash
current=0
while ; do
if ; then
echo ${current}
current=$((${current}+1))
fi
done (1 Reply)
Hey,
can someone explain me this script?
i=0
while read WORT
do
echo $WORT|grep a>/dev/null || echo$WORT|grep B>dev/null || let i=$i+1
done
echo $i
The first lane initializie the variable i with the value of 0.
The loop line has 3 different options because of ||. The only option I... (10 Replies)
Discussion started by: newuser21
10 Replies
LEARN ABOUT MOJAVE
cron
CRON(8) BSD System Manager's Manual CRON(8)NAME
cron -- daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron [-s] [-o] [-x debugflag[,...]]
DESCRIPTION
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in /usr/lib/cron/tabs. There should be no
need to start it manually. See /System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into
memory. The cron utility also searches for /etc/crontab which is in a different format (see crontab(5)).
The cron utility then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current
minute. When executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable
in the crontab, if such exists).
Additionally, cron checks each minute to see if its spool directory's modification time (or the modification time on /etc/crontab) has
changed, and if it has, cron will then examine the modification time on all crontabs and reload those which have changed. Thus cron need not
be restarted whenever a crontab file is modified. Note that the crontab(1) command updates the modification time of the spool directory
whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such as the switches between the standard
time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a time interval that disappears (for
example, during the switch from standard time) to daylight saving time or is duplicated (for example, during the reverse switch),
then it is handled in one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the disappearing or duplicated interval.
In other words, if the job had run within one hour before the GMT offset change (and cron was not restarted nor the crontab(5)
changed after that) or would run after the change at the next hour. They work as always, skip the skipped time or run in the added
time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they are not skipped nor executed twice
(unless cron is restarted or the user's crontab(5) is changed during such a time interval). If an interval disappears due to the GMT
offset change, such jobs are executed at the same absolute point of time as they would be in the old time zone. For example, if
exactly one hour disappears, this point would be during the next hour at the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes, to be compatible with the old (default)
behavior. If both options -o and -s are specified, the option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma separated debugflag identifiers must
be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
SEE ALSO crontab(1), launchctl(1), crontab(5), launchd.plist(5), launchd(8)AUTHORS
Paul Vixie <paul@vix.com>
BSD June 17, 2007 BSD