[NTLUG:Discuss] Where do I look to find why startproc is ignore -p?

[Stephen Davidson]

SuSE 10.1.

The cracked thing is, some of the other processes started in this manner
DO have pid files created.

I am attaching the file for your convenience.  I figured out an viable
'hack' in the meantime;
1) Turn off all application logging & output
2) Turn ON startproc verbose.
3) Capture the only thing output by startproc verbose (the PID), and
store in a file.

The other proc commands can then use this PID as part of their
processing and operate normally.

One other thing I noticed, if there is another server process based on
the same binary (in this case, a Java Based App Server), startproc will
NOT start the process, but report that it is already running.

I am completely stumped on this.

Help?

-Steve

Wayne Walker wrote:
> What distro?  (startproc isn't a standard command, more probably it's
> a shell helper function used in some distro's init.d scripts?)
> 
> On Tue, Dec 04, 2007 at 07:08:49PM -0600, Stephen Davidson wrote:
> Greetings.
> 
> Where do I look to find out why startproc is not creating a PID file???
>  Any idea what the cause could be?  For obvious reasons, this completely
> kills the functionality for the 'stop' command for an init script.
> 
> I have been unable to find anything on Google.
> 
> Help?
> 
> -Steve
>>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pipes
Url: /pipermail/discuss/attachments/20071205/cbf03f65/attachment.asc