My test script is:
If I am using only name, without full path, i am getting error:
But if I am using full path in script, then i am getting error:
Which directory or file not exist? I was trying to define PATH - opt/spots-pms/bin/ in /etc/default/cron, but same result...
And again if i am running from command line its ok.
Last edited by pludi; 10-28-2009 at 06:39 AM..
Reason: code tags, please...
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,
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)
Hi, I posted this in the Solaris forum but I think this one would be more appropriate.
I created a script starting with the following lines:
#!/usr/bin/ksh
flag=n
export flag
typeset -i quant=0
(...)
When running it I'm getting the following 2 errors:
/tmp/tstscript/testfail.ksh:... (9 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 All,
i have implemented Rsync in my source and destination server. while running through command prompt it is working fine:
ksh rsync_bravo_db.ksh usa0300uz1252.apps.mc.xerox.com /uv1402/u207/home/bravodba/bin/rsync-3.0.9/config/mrsx_rsync.cfg
but later on i created a another ksh and... (4 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 DEBIAN
pmsd
PMSD(8) System Manager's Manual PMSD(8)NAME
pmsd - Periodically Manic System Daemon. Manages the bizzare and sometimes unexplainable behavior exhibited by computers.
SYNOPSIS
pmsd [-bcfmp]
DESCRIPTION
pmsd is a rogue daemon that is spawned on a semi-regular schedule by init(8). Most of the unusual and quirky behavior associated with mis-
behaving computers can be attributed to pmsd.
pmsd has a number of command-line options, invoked at run-time by init(8). The ps(1) command will occasionally display the current
options, but only if pmsd feels like revealing them. This is usually not the case. pmsd can be manually invoked by the pms(8) command. Make
sure there is not a pmsd process already running when you use pms(8); you don't want to be on a system with multiple instances of pmsd run-
ning.
With no flags, pmsd runs with the default -m option, and any others it feels like using.
OPTIONS -b Bloat. Files randomly grow in size, filling up filesystems and causing quotas to be exceeded.
-c Craving. System becomes hungry, eating magnetic tapes, CD-ROM discs, floppies, and anything else a hapless user loads into a remov-
able media drive.
-f Fatigue. System will pause for a random period of time. It is important to leave the system alone during this time. Attempts to coax
the machine into normal operation could cause the spontaneous activation of all command-line switches. This is to be avoided.
-m Mood swings. Process priorities and nice values are altered randomly. Swapping usually occurs with no warning, even when memory is
available. This is the default behavior.
-p Peeved. One or more users are selected as targets of the system's anger. Files are deleted, e-mail copied to /etc/motd, and any
Usenet articles posted by the targets are crossposted to misc.test and alt.flame.
NOTES
When pmsd is invoked by using the pms(8) command, pmsd ignores any command-line switches and does what it damned well pleases.
SEE ALSO pms(8)BUGS
There are no bugs; how could you ask that?
HISTORY
Written by Eric L. Pederson <eric@bofh.org.uk>.
25 March 1996 PMSD(8)