Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

2010-10-01 Thread Jilles Tjoelker
On Thu, Sep 30, 2010 at 09:03:33AM +0200, Ed Schouten wrote: > * Jeremy Chadwick wrote: > > 1) "mysqld_safe > /dev/null 2>&1 &" never released the tty > > 2) "nohup mysqld_safe > /dev/null 2>&1 &" did release the tty > What happens if you run the following command? > daemon -cf mysqld_safe

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

2010-09-30 Thread Paul Mather
On Sep 30, 2010, at 3:56 AM, Jeremy Chadwick wrote: > The diff is pretty obvious/simple (2 line change), so the other > databases/mysqlXX-server ports can be upgraded in the same manner. > > --- files/mysql-server.sh.in.orig 2010-03-27 03:24:53.0 -0700 > +++ files/mysql-server.sh.in

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

2010-09-30 Thread Jeremy Chadwick
On Thu, Sep 30, 2010 at 08:53:07AM -0400, Paul Mather wrote: > On Sep 30, 2010, at 3:56 AM, Jeremy Chadwick wrote: > > > The diff is pretty obvious/simple (2 line change), so the other > > databases/mysqlXX-server ports can be upgraded in the same manner. > > > > --- files/mysql-server.sh.in.orig

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

2010-09-30 Thread Alex Dupre
Jeremy Chadwick ha scritto: > Until rc(8) can be updated to support daemon(8) natively, This would be the Right Thing IMHO. > the ~76 ports > which Do The Wrong Thing(tm) should get updated to do it this way. Ones > like mysqlXX-server should be placed high on the priority list given > their pop

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

2010-09-30 Thread Jeremy Chadwick
On Thu, Sep 30, 2010 at 09:30:25AM +0200, Alex Dupre wrote: > Jeremy Chadwick ha scritto: > > Until rc(8) can be updated to support daemon(8) natively, > > This would be the Right Thing IMHO. > > > the ~76 ports > > which Do The Wrong Thing(tm) should get updated to do it this way. Ones > > like

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

2010-09-30 Thread Jeremy Chadwick
On Thu, Sep 30, 2010 at 09:03:33AM +0200, Ed Schouten wrote: > Hi Jeremy, > > * Jeremy Chadwick wrote: > > 1) "mysqld_safe > /dev/null 2>&1 &" never released the tty > > 2) "nohup mysqld_safe > /dev/null 2>&1 &" did release the tty > > What happens if you run the following command? > > da

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

2010-09-30 Thread Ed Schouten
Hi Jeremy, * Jeremy Chadwick wrote: > 1) "mysqld_safe > /dev/null 2>&1 &" never released the tty > 2) "nohup mysqld_safe > /dev/null 2>&1 &" did release the tty What happens if you run the following command? daemon -cf mysqld_safe The point is that FreeBSD's pts(4) driver only dealloca

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

2010-09-30 Thread Adam Vande More
On Thu, Sep 30, 2010 at 1:51 AM, Jeremy Chadwick wrote: > Something interesting I've come across which happens on both RELENG_7 > and RELENG_8 (indicating it's not a problem with the older tty code or > the newer pty/pts code), and it's reproducible on Linux (sort of...). > > mysqld_safe appears t

mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

2010-09-29 Thread Jeremy Chadwick
Something interesting I've come across which happens on both RELENG_7 and RELENG_8 (indicating it's not a problem with the older tty code or the newer pty/pts code), and it's reproducible on Linux (sort of...). mysqld_safe appears to hold a pty/tty open even after the process has been backgrounded