10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
2. Shell Programming and Scripting
When i am working with cron i given the command as crontab - e | grep runjob.sh.I though my command is wrong and i closed it by ctrl+D.After that when i need to open the cron with crontab -e its not opening its giving some number 22667 and when i given crontab -l its working fine i can see all... (5 Replies)
Discussion started by: bhas85
5 Replies
3. UNIX for Dummies Questions & Answers
Hi Newbie here
I am having problems with automating sFTP transfers.
Just to save time - SCP is not an option as sFTP is stipulated by controllers of far end server.
Ineed to automate sFTP transfer of a single file, once a day to a remote server to which i have no control over.
I am using:... (6 Replies)
Discussion started by: robbien
6 Replies
4. Shell Programming and Scripting
Hi,
I have a shell script as below:
ORACLE_HOME=/usr/local/opt/oracle/product/dev
export ORACLE_HOME
PATH=$PATH:$ORACLE_HOME/bin:/usr/bin
export PATH
OUTFILE=/export/home/`basename $0`.out
export OUTFILE
export IDEN
df -k . | tail -1 | read a b c d e f
echo $a >> $OUTFILE
echo $b... (4 Replies)
Discussion started by: Abhinav Pandey
4 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Before I start, I would like to inform that, I went through all FAQs and other threads before posting here.
I 'm trying to schedule a shell script on cygwin using cron. No matter what I do I don't seem to get the cron job executing my bash script.
My script is temp.sh
echo `date` >... (4 Replies)
Discussion started by: shash
4 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I have problem in executing a shell script. When the shell script is executed at the shell prompt the script works successfully but when the same script is run as a cron job it fails to execute the files called within the shell script.
I have scheduled the job in my crontab file as
... (6 Replies)
Discussion started by: forumthreads
6 Replies
7. Shell Programming and Scripting
Hi;
I'm facing the problem with my script like below
30 0 * * * /data/SCRIPT/LOADLOGS/loadata1.sh 2 1 >> /tmp/loaddata.txt
loadata1.sh calling a another 2 scripts which we need to exe in sequence.
when it perform by cron jon, sometimes it just can process 20 recs or less or nothing but... (6 Replies)
Discussion started by: izai
6 Replies
8. AIX
hello
I use a script to give me the number of users, at each hour.
this script read a file where there is the number of users for each hour and for each month (so 12 files per year).
If i execute the script (root), it is ok, i have xxx users for each hour.
if I put the script in the cron... (1 Reply)
Discussion started by: pascalbout
1 Replies
9. Shell Programming and Scripting
Hello All,
One of my shell scripts was working fine till a few days back. It was scheduled in the cron. But yesterday i made some modifications to the script. The script works fine when i run it from the prompt. But it is not working when in runs from cron. Can someone help me out from this. (4 Replies)
Discussion started by: Raiden
4 Replies
10. Shell Programming and Scripting
I've written a csh shell script to number each line of a file.
Firstly, the program count the number of the file and create a file with number at the front. Then, combine the file together.
when i call the program manually, it works.However, when i set it in the cronjob, the output always leaves... (3 Replies)
Discussion started by: fung_donald
3 Replies
sv(8) System Manager's Manual sv(8)
NAME
sv - control and manage services monitored by runsv(8)
SYNOPSIS
sv [-v] [-w sec] command services
/etc/init.d/service [-w sec] command
DESCRIPTION
The sv program reports the current status and controls the state of services monitored by the runsv(8) supervisor.
services consists of one or more arguments, each argument naming a directory service used by runsv(8). If service doesn't start with a dot
or slash and doesn't end with a slash, it is searched in the default services directory /etc/service/, otherwise relative to the current
directory.
command is one of up, down, status, once, pause, cont, hup, alarm, interrupt, 1, 2, term, kill, or exit, or start, stop, restart, shutdown,
force-stop, force-reload, force-restart, force-shutdown.
The sv program can be sym-linked to /etc/init.d/ to provide an LSB init script interface. The service to be controlled then is specified
by the base name of the ``init script''.
COMMANDS
status Report the current status of the service, and the appendant log service if available, to standard output.
up If the service is not running, start it. If the service stops, restart it.
down If the service is running, send it the TERM signal, and the CONT signal. If ./run exits, start ./finish if it exists. After it
stops, do not restart service.
once If the service is not running, start it. Do not restart it if it stops.
pause cont hup alarm interrupt quit 1 2 term kill
If the service is running, send it the STOP, CONT, HUP, ALRM, INT, QUIT, USR1, USR2, TERM, or KILL signal respectively.
exit If the service is running, send it the TERM signal, and the CONT signal. Do not restart the service. If the service is down, and
no log service exists, runsv(8) exits. If the service is down and a log service exists, send the TERM signal to the log service.
If the log service is down, runsv(8) exits. This command is ignored if it is given to an appendant log service.
sv actually looks only at the first character of these commands.
Commands compatible to LSB init script actions
status Same as status.
start Same as up, but wait up to 7 seconds for the command to take effect. Then report the status or timeout. If the script ./check
exists in the service directory, sv runs this script to check whether the service is up and available; it's considered to be avail-
able if ./check exits with 0.
stop Same as down, but wait up to 7 seconds for the service to become down. Then report the status or timeout.
reload Same as hup, and additionally report the status afterwards.
restart
Send the commands term, cont, and up to the service, and wait up to 7 seconds for the service to restart. Then report the status or
timeout. If the script ./check exists in the service directory, sv runs this script to check whether the service is up and avail-
able again; it's considered to be available if ./check exits with 0.
shutdown
Same as exit, but wait up to 7 seconds for the runsv(8) process to terminate. Then report the status or timeout.
force-stop
Same as down, but wait up to 7 seconds for the service to become down. Then report the status, and on timeout send the service the
kill command.
force-reload
Send the service the term and cont commands, and wait up to 7 seconds for the service to restart. Then report the status, and on
timeout send the service the kill command.
force-restart
Send the service the term, cont and up commands, and wait up to 7 seconds for the service to restart. Then report the status, and
on timeout send the service the kill command. If the script ./check exists in the service directory, sv runs this script to check
whether the service is up and available again; it's considered to be available if ./check exits with 0.
force-shutdown
Same as exit, but wait up to 7 seconds for the runsv(8) process to terminate. Then report the status, and on timeout send the ser-
vice the kill command.
try-restart
if the service is running, send it the term and cont commands, and wait up to 7 seconds for the service to restart. Then report the
status or timeout.
Additional Commands
check Check for the service to be in the state that's been requested. Wait up to 7 seconds for the service to reach the requested state,
then report the status or timeout. If the requested state of the service is up, and the script ./check exists in the service direc-
tory, sv runs this script to check whether the service is up and running; it's considered to be up if ./check exits with 0.
OPTIONS
-v If the command is up, down, term, once, cont, or exit, then wait up to 7 seconds for the command to take effect. Then report the
status or timeout.
-w sec Override the default timeout of 7 seconds with sec seconds. This option implies -v.
ENVIRONMENT
SVDIR The environment variable $SVDIR overrides the default services directory /etc/service/.
SVWAIT The environment variable $SVWAIT overrides the default 7 seconds to wait for a command to take effect. It is overridden by the -w
option.
EXIT CODES
sv exits 0, if the command was successfully sent to all services, and, if it was told to wait, the command has taken effect to all ser-
vices.
For each service that caused an error (e.g. the directory is not controlled by a runsv(8) process, or sv timed out while waiting), sv
increases the exit code by one and exits non zero. The maximum is 99. sv exits 100 on error.
If sv is called with a base name other than sv: it exits 1 on timeout or trouble sending the command; if the command is status, it exits 3
if the service is down, and 4 if the status is unknown; it exits 2 on wrong usage, and 151 on error.
SEE ALSO
runsv(8), chpst(8), svlogd(8), runsvdir(8), runsvchdir(8), runit(8), runit-init(8)
http://smarden.org/runit/
AUTHOR
Gerrit Pape <pape@smarden.org>
sv(8)