06-07-2004
file activity (open/closed) file descriptor info using KORN shell scripting
I am trying to find a way to check the current status of a file. Such as some cron job processes are dependent on the completion of others. if a file is currently being accessed / modified or simply open state I will wait until it is done being processed before attempting the next process on that file. Mainly the final process that zips previous days files up. I want to hold off archiving the previous days file until it is no longer being accessed.
thanks!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi, being very new to Korn Shell Scripting I am hoping that someone here can help me. I want to compare file name in scp/inbox directory to file name stored inside a file in pnt/compare directory.
Hi, being very new to Korn Shell Scripting I am hoping that someone here can help me. I want to... (1 Reply)
Discussion started by: hanie123
1 Replies
2. UNIX for Dummies Questions & Answers
Hi
I'm new to scripting and I don't know where to start. I need to create a script that needs to look for specific files in a specific folder then I need to return the filename, the recordcount, bytecount and checksums. Then I need to write these results into a new file.
I would appreciate... (2 Replies)
Discussion started by: th0123
2 Replies
3. Shell Programming and Scripting
Hello All,
Can someone help me to set a user's password from the script using korn shell. The password change is a one time password after user account creation.
I tried providing the input file as the value for password field but password change requires tty so my password from an input file... (3 Replies)
Discussion started by: solaix14
3 Replies
4. Shell Programming and Scripting
I have made the following simple script:
a=0
let a=$a+1
if "]
then mailx -s "Up" abc@yahoo.com
fi
When I run the above script, I get the following error:
# ./new.ksh
./new.ksh: ]: not found.
Please tell me how to use if here? (6 Replies)
Discussion started by: kamaldeep1986
6 Replies
5. UNIX for Dummies Questions & Answers
which is a gud book to learn advanced korn shell scripting?
i know the basic shell scripting (1 Reply)
Discussion started by: shishirkotkar
1 Replies
6. Shell Programming and Scripting
I am attempting to learn shell programming using o'rielly book "Learning the Korn Shell".
I am finding it pretty difficult to do since the only access I have to unix boxes are running version 99 of ksh.
The book utilizes ksh93 and there appear to be many differences. I can't even follow along... (2 Replies)
Discussion started by: vedder191
2 Replies
7. UNIX for Advanced & Expert Users
I have a scenario to implement in Korn shell script. Here it is..
I need to compare two values to see whether they are same or not. The issue is that the values coming in for comparison can be a string or an integer which can be determined during run time only.
Which korn shell comparison... (2 Replies)
Discussion started by: vani123
2 Replies
8. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
There is a menu driven program and there are some fields to be achived
3. Display contents of all .lst files... (3 Replies)
Discussion started by: jainitai
3 Replies
9. Shell Programming and Scripting
#! /bin/ksh
while read line
do
if ] ; then
echo "no data"
continue;
fi
echo "performing operation on $line"
done < prg.txt (3 Replies)
Discussion started by: Juhi Kashyap
3 Replies
10. Shell Programming and Scripting
Does dialog box works on all kind of shells? I am using korn shell in Linux .
For me dialog is not working :) is there any particular syntax or do we need to have particular OS version or shell env?
#!/bin/ksh
dialog --title "create file" \
--backtitle "shell script practice" \... (1 Reply)
Discussion started by: NarayanaPrakash
1 Replies
cron(1M) System Administration Commands cron(1M)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)
NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)