Date: Wed, 05 Sep 2007 15:06:16 +0400 From: Sergey Matveychuk <sem@FreeBSD.org> To: Russell Jackson <raj@csub.edu> Cc: freebsd-ports@freebsd.org Subject: Re: portupgrade exits immediately when stdin/out closed Message-ID: <46DE8DA8.1030506@FreeBSD.org> In-Reply-To: <46DDE90D.8090700@csub.edu> References: <46DDE90D.8090700@csub.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Russell Jackson wrote: > I'm debugging a problem with portupgrade being used as part of an automated package > handler within puppet (http://puppet.reductivelabs.com). > > The problem is that when the handler executes portupgrade as an external process from > ruby, portupgrade hangs with a script process taking up 100% of the cpu. I suspected that > script isn't designed to be run without a controlling tty. So, I executed portupgrade like > so to test: > > portupgrade --new --batch --yes <port> <&- >&- 2>&- & > > To my surprise, portupgrade exits immediately with a status of 0. I found an old pr > (bin/56166) describing similar behavior. It looks like script was fixed, but portupgrade > still isn't happy. > > This happens with both ports-mgmt/portupgrade and ports-mgmt/portupgrade-devel. > > Suggestions? > portupgrade was fixed to work when tty is not a physical device but file or so. I think you don't want to run portupgade this way really. You have a possibility to brake everything. -- Dixi. Sem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46DE8DA8.1030506>