search for: greppery

Before the official release of icecast2 1.0 (non beta) i would like to see pid file management, ive discussed this before on how to capture the pid, but ended up with alot of bash rigamaroo that mounted to even more headaches. omething in the config file like <pid>/path/to/icecast.pid</pid> I would be willing to donate some bandwidth to xiph, to aleaviate this issue that causes sever

...;s no "pidof" or "killall" here > ... if I need to script something, I use the following which can be > considered ``safe''. (The function is what's doing the job, the rest is > just how I use it stand-alone sometimes). Simple, but effective - no > insane greppery, no conflicts with additional `ps` output, nor pidof > having any problems with itself (it can never have a PPID of 1, so it > won't return its own PID, ever). > > --- snip --- > #!/bin/sh > > # pidof() code by Christoph Moench-Tegeder > # and Michael Erdely (from tech@o...

...ostly, and there's no "pidof" or "killall" here ... if I need to script something, I use the following which can be considered ``safe''. (The function is what's doing the job, the rest is just how I use it stand-alone sometimes). Simple, but effective - no insane greppery, no conflicts with additional `ps` output, nor pidof having any problems with itself (it can never have a PPID of 1, so it won't return its own PID, ever). --- snip --- #!/bin/sh # pidof() code by Christoph Moench-Tegeder # and Michael Erdely (from tech@openbsd.org) # _pidof() { ps -a...

...ot; or "killall" here > > ... if I need to script something, I use the following which can be > > considered ``safe''. (The function is what's doing the job, the rest is > > just how I use it stand-alone sometimes). Simple, but effective - no > > insane greppery, no conflicts with additional `ps` output, nor pidof > > having any problems with itself (it can never have a PPID of 1, so it > > won't return its own PID, ever). > > > > --- snip --- > > #!/bin/sh > > > > # pidof() code by Christoph Moench-Tegeder &gt...