On Fri, 2011-11-04 at 16:34 +0100, Per Jessen wrote:
Roger Oberholtzer wrote:
On Fri, 2011-11-04 at 00:22 +1030, Rodney Baker wrote:
I'd suggest you many need multiple entries in /etc/rc.d/init.d (e.g. 51- <process>.rc, 52-<process>.rc...n-<process>.rc). I'd see the flow something like:
I perhaps could have lived with that. But it 'seems' it is not the rc script name that is behind this. It is the binary that you run. In my case I am running /sbin/vblade. The second call to startproc senses that /sbin/vblade is already running and does nothing. If I make a copy of the binary called /sbin/vblade2, then I can start another.
hi Roger
this is a poor workaround:
create a tiny script, e.g. /sbin/runvblade:
----- #!/bin/sh exec /sbin/vblade --------
You should be able to run "startproc -s /sbin/runvblade" as many times as you want.
Curious. Why would this work? I will of course try it. But I would like to know what is different between running a script and the program direct. Will it 'status' and 'stop' commands to the rc script also work? Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org