04-26-2010
Solution
I wasn't really in a position to add anymore logging as I am not the sys admin.
Thanks for all of your help.
10 More Discussions You Might Find Interesting
1. HP-UX
How to track the pid of a background child process(shell script) from a parent script ?
For example :-
$ sleep 10000 &
4220
where 4220 is the pid of bg process sleep.
Now my requirement is to keep the sleep statement in a shell script(test.ksh) and will be invoking it from... (3 Replies)
Discussion started by: ramkumar
3 Replies
2. UNIX for Dummies Questions & Answers
Is there a command in HP Unix which can be used inside a K shell to find out the maximum number of processes (PIDs) a pc can generate?
Any help will be greatly appreciated.
Steve (8 Replies)
Discussion started by: stevefox
8 Replies
3. Shell Programming and Scripting
I am trying to write a Shell script wherein the shell needs to read a list of PID in the File $stat/bin/Process and compare it to the PID of the processes running on a server.
Also the script should return KO(not OK) with corresponding label :-
a) When an environmental variable not... (2 Replies)
Discussion started by: marconi
2 Replies
4. Shell Programming and Scripting
Hi,
There is a file having a list of running PIDs and another file having a list of registered PIDs. How can we check if the number of running PIDs are less or more than the registered PIDs, comparing the total no. in each and also each value.
Request you to pls give your inputs.
Thanks a... (2 Replies)
Discussion started by: marconi
2 Replies
5. Shell Programming and Scripting
Hi,
There is a file having a list of running PIDs (pid_process) and another file having a list of registered PIDs (pid_regieter).
I want to check if:-
a) there is at least one running PID that does not correspond to a
registered PID (listing the PID not registered in the file)
... (1 Reply)
Discussion started by: marconi
1 Replies
6. Shell Programming and Scripting
I have a script that conducts some SSH calls and I would like to capture the child info so that I can do a sleep and then a cleanup to make sure they do not stay out there as ghosts.
I was told I could do something like this...
#!/bin/sh
for m = job1, job2, job3
x=1... (4 Replies)
Discussion started by: LRoberts
4 Replies
7. HP-UX
Hi,
I know this has been discussed a number of time but i could not get the exact answer. So need help again.
Issue:
The two command for same file system shows different size.
du -sk shows toatl size is 12780685 KB while df -k 45289229 used allocated Kb
/oxt/mantran/bin $ du -sk... (8 Replies)
Discussion started by: malaya_17
8 Replies
8. Shell Programming and Scripting
Hey,
So I'm new to shell scripting, and I'm trying to write one for my lab that will keep down the work load by deleting processes that are left over from previous sessions.
Basically I want it to do three things.
1) Check the processes running
2) See if that person is logged on.
3) if... (2 Replies)
Discussion started by: prgoodwin
2 Replies
9. Shell Programming and Scripting
Hi there !!!
I am writing a script to kill the pids on different linux boxes :cool:
the output of my command gives the pids running on that box, but how can I kill all the pids without looping? :confused:
Code:
ssh $i ps -fu $USER | grep ManServer | grep -v grep | awk '{print $2}' | kill
... (4 Replies)
Discussion started by: prany_cool
4 Replies
10. Shell Programming and Scripting
im looking for a portable way to get the PID of the script that is running, and to get every other PIDs that are spawned from it.
and by ever other PIDs, i presume, that would be "child processes".
however, i want to shy away from using any command that is not available on every single unix... (1 Reply)
Discussion started by: SkySmart
1 Replies
LEARN ABOUT OPENDARWIN
cron
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)