12-14-2007
Thanks porter, but there are hundreds of scripts running, and they are either Ksh or Perl scripts. Do you mean a separate wrapper for every script? A common wrapper is not possible, since I am not supposed to modify cron entry.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have 2 start and stop sh.
Start sh
--------
This will start few processes.
Example code:
echo "start process : lgz200 /pipe=test_jobs"
nohup lgz200 /db=test/test1@test1 /pipe=test_jobs > ../log/lgz200_j.log &
echo "echo \"stop process (pid=$!): lgz200 /pipe=test_jobs\"" >>... (3 Replies)
Discussion started by: maldini
3 Replies
2. UNIX for Advanced & Expert Users
How can I tell my syslog.conf to log "syslog start/stop/restart" messages on a Solaris box? (1 Reply)
Discussion started by: SunnyK
1 Replies
3. Shell Programming and Scripting
HI
I am using below code to start and stop servers but it is not working ,how to run the script please suggest me ,if any errors in the script please let me know.
#!/bin/bash
IMS_START="/Webserver/AppServer/bin/startServer.sh"
IMS_STOP="/Webserver/AppServer/bin/stopServer.sh"
case "$1" in
... (1 Reply)
Discussion started by: RG18173
1 Replies
4. Shell Programming and Scripting
Hey!
I'm working on a script that will add a user, create some configfiles, and add a crontab for the user.
The crontab looks like the following:
@reboot /home/user/program config.conf &
I would like for this process to start at the end of my script under the corresponding username by... (0 Replies)
Discussion started by: noratx
0 Replies
5. Solaris
Please anyone tell me
In my last interview the HR asks me how to monitor, start,stop & kill the various processes and subprocesses.
Please anyone explain me clearly. It's my personal request (3 Replies)
Discussion started by: suneelieg
3 Replies
6. UNIX for Dummies Questions & Answers
Is there any functional difference between:
issuing separate stop/start commands like this;
super (handler) (instance) stop
super (handler) (instance) start
versus issuing a single recycle command like this;
super (handler) (instance) restart (3 Replies)
Discussion started by: Newbix
3 Replies
7. SuSE
Hi there,
I've install a testserver with SLES 11.0! I'll install/test XEN + WebServer not all things at the moment!
In a first time, I'd like to stop all unuse processes... but I don't understand all processes!
As someone a list of all processes with his signification and which should/could... (3 Replies)
Discussion started by: hiddenshadow
3 Replies
8. UNIX for Advanced & Expert Users
If we have 3 process to write to same log file at the same time like below. will it cause the data outdated because the multiple process writing same time? It this a safe way to keep the log for multiple process?
p1 >> test.log &;
p2 >> test.log &;
p3 >> test.log &
Thanks, (1 Reply)
Discussion started by: casttree
1 Replies
9. Shell Programming and Scripting
Hey
Excuse me if this question is repeated everywhere but I am still new with scripting and I couldn't apply what I found to my case :confused::confused:
I am trying to run a rec process on a ssh client and at the same time play a file from my computer so i tried this
#!/bin/bash
echo... (3 Replies)
Discussion started by: Antaha
3 Replies
10. Red Hat
How do I find the process ( which might got completed ) which were ran at specific time.
for e.g. I should be able to find below process after 2 hrs if I find by time 04:00
myuser 23285 22522 0 04:00 pts/0 00:00:00 /home/myuser/bin/abc.ksh (3 Replies)
Discussion started by: sameermohite
3 Replies
LEARN ABOUT PHP
systemd-sysv-generator
SYSTEMD-SYSV-GENERATOR(8) systemd-sysv-generator SYSTEMD-SYSV-GENERATOR(8)
NAME
systemd-sysv-generator - Unit generator for SysV init scripts
SYNOPSIS
/lib/systemd/system-generators/systemd-sysv-generator
DESCRIPTION
systemd-sysv-generator is a generator that creates wrapper .service units for SysV init[1] scripts in /etc/init.d/* at boot and when
configuration of the system manager is reloaded. This will allow systemd(1) to support them similarly to native units.
LSB headers[2] in SysV init scripts are interpreted, and the ordering specified in the header is turned into dependencies between the
generated unit and other units. The LSB facilities "$remote_fs", "$network", "$named", "$portmap", "$time" are supported and will be turned
into dependencies on specific native systemd targets. See systemd.special(5) for more details.
SysV runlevels have corresponding systemd targets (runlevelX.target). The wrapper unit that is generated will be wanted by those targets
which correspond to runlevels for which the script is enabled.
systemd does not support SysV scripts as part of early boot, so all wrapper units are ordered after basic.target.
systemd-sysv-generator implements systemd.generator(7).
SEE ALSO
systemd(1), systemd.service(5), systemd.target(5)
NOTES
1. SysV init
https://savannah.nongnu.org/projects/sysvinit
2. LSB headers
http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
systemd 237 SYSTEMD-SYSV-GENERATOR(8)