Many years ago I found a way to force the shell for a cron job. It's probably not the best way to do it and it may be as bakunin has suggested. What I coded within cron (and it was running some 15 years before we moved platform ) was something like this mess:
Code:
00 07 * * * /usr/bin/ksh %/usr/bin/my_ksh_script
I can't remember how I worked this out or why I thought it was a good idea, but it seemed to work. The % marker did something special and it worked, but the machine it was on is now gone by 2 years, so I can't be sure. I remember thinking that /usr/bin was a great place to put my code, seeing as it was in everyone's path. I think I'd recommend against that now!
I must say that what you have all looks to be in order. Perhaps a quick test script could be knocked together along the lines of:
Code:
#!/bin/ksh
ps -f>/tmp/ps-f
ps -l>/tmp/ps-l
Have a look at the processes listed to see if that gives you more hints.
Hi,
I made this script for TRU Unix 5.1 OS based Node.
When the script was run manually all the commands were running properly. But when it was run from Crontab, one command is not running.
This command is not running when the script is running from Crontab:
#... (2 Replies)
I am facing a strange issue while running a script(eg A) from the crontab entry
the script calls one more script(eg B) within it
now when i run the script A manually(with nohup) it also executes the script B (embedded inside it) as expected.
but when i run the script A from the crontab entry... (7 Replies)
Hi all,
I wrote small script for Solaris and when I am running it through command prompt its ok, but when I trying to run it using crontab, i am getting error like:
ld.so.1: dbloader: fatal: libACE.so: open failed: No such file or directory
/tmp/file.sh: line 5: 8304 Killed ... (4 Replies)
Hi,
I'm trying the backup a few information commands of my Check Point FW (it's on a SPLAT linux machine). This is the script I wrote:
#!/bin/bash
cd /var/tmp/
file1=netstat_`/bin/date +%d%m%y`.txt
file2=ifconfig_`/bin/date +%d%m%y`.txt
file3=cpstatos_`/bin/date +%d%m%y`.txt... (2 Replies)
I am trying to use the CRON utility in Fedora 11 & CentOS...
I intend to run a script which pops up a warning message every hour and i made the following entry using "CRONTAB -e "
* * * * * sh /bin/myscript.sh
But this does not seem to be running.
Another thing to note is that,... (4 Replies)
Hi,
I have created the below script,
set -x
# Set the Path of Environment file
ENV_FILE_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/bin
LOG_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/log
export ENV_FILE_DIR
export LOG_DIR
# Set Audit Environment
. ${ENV_FILE_DIR}/QDM.env... (8 Replies)
Hi All,
I am having the below script to be run from crontab, it it doesnt run.
1 * * * * /home/cobr_ext/test.sh > /home/cobr_ext/temp.txt
when i run i manally it runs without any issues.
Could please help me as to why doesnt it run the script.:( (7 Replies)
I am facing an issue where sometimes crontab is running script with some delay.
Below is the stmt in script and it is the only stmt in script.
echo "running at `date` " >> CRONCHECK.log
Below is the cron entry.
0 11 * * * CRONCHECK.sh
Below is the time of run each day.
running at Fri... (8 Replies)
Hi guys!
I created a backup script that works fine when I run manually, but when I put a crontab job to execute it the result are not the expected. (not a time problem).
Here is my script:
bash-3.00# cat /bk_tool/backup2.sh
#!/usr/bin/csh
clear
set DIR_HOST='SCP08'
... (3 Replies)
Hi!
I'm using a RaspberryPi with standard Raspbian.
Currently I'm working on some sort of weather station.
For now I have three python scripts - one which is updating txt files for website - update1m.py ( it will not be necessary in few next days so I'll delete it) , second one for updating... (4 Replies)
Discussion started by: bartocham
4 Replies
LEARN ABOUT SUNOS
cssd
cssd(1M) System Administration Commands cssd(1M)NAME
cssd - daemon which invokes and watches the CSs
SYNOPSIS
/usr/sbin/cssd [-f filename]
AVAILABILITY
SUNWjfpu
DESCRIPTION
cssd is the command which invokes and watches CS available in MLE (Multi Language Environment). After five seconds of the ending (includ-
ing abnormal termination) of a CS, cssd re-invokes the CS.
CS STARTING INFORMATION FILE
In a CS starting information file, /etc/css.conf by default, some CS starting information directories are described. This file can be cus-
tomized. cssd reads /etc/css.conf to get CS starting information directories, and then it invokes all executable files in the directories.
Usually, each CS itself is not placed in the directories and is invoked indirectly from a script in one of the directories.
CS STARTING SCRIPT
A CS starting script is located in a CS starting information directory. cssd reads all CS starting information directories in the sequence
specified in /etc/css.conf and finds to invoke all CS starting scripts. If two or more scripts which have the same filename are found,
cssd invokes only the first one.
UPDATING CS STARTING INFORMAION
When cssd receives signal SIGHUP , it re-reads /etc/css.conf and re-finds all CS starting scripts, and then restarts, starts or terminates
each script according to the following conditions.
A script whose modified time is changed (is to be restarted) A script which is newly added (is to be started) A script which is
deleted (is to be terminated)
TO TERMINATE
When cssd receives signal SIGTERM, it sends SIGTERM to each CS under the cssd's management and terminates itself (in general, each CS also
terminates with the signal).
ERROR INFORMATION
As a facility of daemon, cssd sends error information at level `err' , and invoke/re-invoke information at level `notice' to syslogd(1M).
OPTION -f filenaSpecify a CS starting information file. Without this option, /etc/css.conf is used.
FILE
/etc/css.conf file for the information of CSs by default
SEE ALSO css.conf(4), syslogd(1M)BUGS
If a CS starting script is programmed so that itself is exec-ed by a CS, cssd understands that the process of the CS starting script is
terminated in spite of the CS's termination, and so puts syslog message out.
SunOS 5.10 10 Jan 2003 cssd(1M)
02-24-2011
) was something like this mess: