Hi,
I have a script which I am able to run from command line. When I put this in cron, it fails and gives the following message:
ld.so.1: /d00/documentum/product/5.2.5/bin/dmbasic: fatal: libdmcl40.so: open failed: No such file or directory
The ksh script looks like this:
# Set this... (1 Reply)
Hi ,
I have an issue with cron job that i have scheduled today. The problem is that when i run this script in command prompt it work good giving me the desired results but if i schedule this to run using cron job it failes giving a "syntax error in line 11 :$"..... Can anyone look into this and... (6 Replies)
I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
This is regarding my cron job. My cron entry
30 * * * 1-5,0 /work1/informix/sample/script1.sh
31 * * * 1-5,0 /work1/informix/sample/script2.sh
Every 30 mins script1.sh is run. (mon thru friday and sunday)
Every 30 mins script2.sh is run. (mon thru friday and sunday)
This is based on the... (3 Replies)
Hi ,
I want to run script every minute so i added .
cron entry as below usning crontab -e
looks like
*/1 * * * * sh /home/sai/http_sim/http_start.sh
but cron job is not running ?
any way to start the cron or something ?
Thanks,
Raghavendra (2 Replies)
I want to update svn code using a nightly job using cron, i have created a job in cron as,
30 17-19 * * 1-5 /home/saprab/svnUpdate.sh <branch> <svnusername> <svnpassword> >> <logfile> 2>&1
svnUpdate.sh :
===============
#!/bin/bash
branch=$1
svnuser=$2
svnpass=$3
cd ${branch}... (2 Replies)
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Dear Members
Seeking you help on my issue.
this script need to run on every end of month.i configured as below.
but it runs everyday.
why
0 9 28-31 * * ] && /usr/bin/bash /u01///scripts/e.sh (3 Replies)
My Friends
I want to run a script only at the end of month.but i tried below cront entry its not working. pls help
0 9 28-31 ] && /usr/bin/bash /u01/app/scripts/CX-eom.shOs Details: AIX 7.1.0.0
Please use CODE tags as required by forum rules! (5 Replies)
Discussion started by: ded325
5 Replies
LEARN ABOUT OSF1
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS --restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO debhelper(7)AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)