Re: General note on rc scripts and daemonizing

2010-07-23 Thread Dominic Fandrey
On 17/07/2010 12:56, Ed Schouten wrote: > ... > > This has various implications. The most important one I can think of, is > that the daemon can still do open("/dev/tty", ...) if it wants and spam > your TTY, even if the daemon is running as user `nobody'. This also > means that if you run the rc

Re: General note on rc scripts and daemonizing

2010-07-21 Thread Tom Rhodes
Hey, On Tue, 20 Jul 2010 17:25:03 -0700 Doug Barton wrote: > On 07/20/10 16:46, Jos Backus wrote: > > Fwiw, I would much prefer FreeBSD ship with some sort of process supervisor > > a la daemontools. > > That's an interesting idea, but until we have someone willing to > actually do that work we

Re: General note on rc scripts and daemonizing

2010-07-20 Thread Doug Barton
On 07/20/10 16:46, Jos Backus wrote: > Fwiw, I would much prefer FreeBSD ship with some sort of process supervisor > a la daemontools. That's an interesting idea, but until we have someone willing to actually do that work we need to deal with what we have. Doug -- Improve the effectiv

Re: General note on rc scripts and daemonizing

2010-07-20 Thread Jos Backus
Fwiw, I would much prefer FreeBSD ship with some sort of process supervisor a la daemontools. Jos ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr.

Re: General note on rc scripts and daemonizing

2010-07-20 Thread Doug Barton
On Tue, 20 Jul 2010, Greg Larkin wrote: Hi Doug, Thank you for the useful background information and ideas about how to proceed forward. I'll put this task on my list (hah!) and see how much progress I can make. Glad to help! :) -- Improve the effectiveness of your Internet presen

Re: General note on rc scripts and daemonizing

2010-07-20 Thread Greg Larkin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doug Barton wrote: > On Tue, 20 Jul 2010, Greg Larkin wrote: [...] >> Anyway, here are some examples for daemonizing processes that don't >> already have support for doing it themselves: >> >> Daemonizing an executable without internal daemon support:

Re: General note on rc scripts and daemonizing

2010-07-20 Thread Doug Barton
On Tue, 20 Jul 2010, Greg Larkin wrote: Ed Schouten wrote: Hello port maintainers, I think I'd better send an email about this to ports@, because I've seen it in various places and it is getting a bit tiresome to mail all port authors individually. Unfortunately not all port maintainers foll

Re: General note on rc scripts and daemonizing

2010-07-20 Thread Greg Larkin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ed Schouten wrote: > Hello port maintainers, > > I think I'd better send an email about this to ports@, because I've seen > it in various places and it is getting a bit tiresome to mail all port > authors individually. > > I've seen various cases in

Re: General note on rc scripts and daemonizing

2010-07-17 Thread Anonymous
jhell writes: > Also another use with the case above. Running top(1) instead of su(1) > you should see the same symptoms. > Use `-f' option in daemon(8). Otherwise it'd still spam to tty. $ daemon top $ procstat -f $(pgrep top) PID COMM FD T V FLAGSREF OFFSET PRO NAME

Re: General note on rc scripts and daemonizing

2010-07-17 Thread jhell
On Sat, 17 Jul 2010 18:43, jhell wrote: In Message-Id: On Sat, 17 Jul 2010 06:56, Ed Schouten wrote: In Message-Id: <20100717105658.gv1...@hoeg.nl> Hello port maintainers, I think I'd better send an email about this to ports@, because I've seen it in various places and it is getting a bit

Re: General note on rc scripts and daemonizing

2010-07-17 Thread jhell
On Sat, 17 Jul 2010 06:56, Ed Schouten wrote: In Message-Id: <20100717105658.gv1...@hoeg.nl> Hello port maintainers, I think I'd better send an email about this to ports@, because I've seen it in various places and it is getting a bit tiresome to mail all port authors individually. I've seen

General note on rc scripts and daemonizing

2010-07-17 Thread Ed Schouten
Hello port maintainers, I think I'd better send an email about this to ports@, because I've seen it in various places and it is getting a bit tiresome to mail all port authors individually. I've seen various cases in the past where people write rc scripts that do the following: command="