On Fri, 11 Jan 2002, Wichert Akkerman wrote:
> Previously Henrique de Moraes Holschuh wrote:
> > Please tell me one good reason not to use the init.d script interface to
> > muck around with daemons _in maintainer scripts_?
>
> The --exec option for start-stop-daemon. This option is very useful: i
Previously Henrique de Moraes Holschuh wrote:
> Please tell me one good reason not to use the init.d script interface to
> muck around with daemons _in maintainer scripts_?
The --exec option for start-stop-daemon. This option is very useful: it
gives start-stop-daemon the ability to verify that it
Michael Banck <[EMAIL PROTECTED]> writes:
> On Fri, Jan 11, 2002 at 04:49:19PM +, Mark Brown wrote:
> > > You can't, in general, close *all* open file descriptors. OPEN_MAX
> > > may not exist (and I would guess that it doesn't on the HURD).
> >
> > If OPEN_MAX is undefined you could always
On Fri, Jan 11, 2002 at 04:49:19PM +, Mark Brown wrote:
> > You can't, in general, close *all* open file descriptors. OPEN_MAX
> > may not exist (and I would guess that it doesn't on the HURD).
>
> If OPEN_MAX is undefined you could always use INT_MAX :-) .
I bet INT_MAX does not exist on Hu
On Fri, Jan 11, 2002 at 04:49:19PM +, Mark Brown wrote:
> On Fri, Jan 11, 2002 at 10:34:18AM -0600, Steve Greenland wrote:
>
> > You can't, in general, close *all* open file descriptors. OPEN_MAX
> > may not exist (and I would guess that it doesn't on the HURD). It's
> > completely reasonable
On Fri, Jan 11, 2002 at 10:34:18AM -0600, Steve Greenland wrote:
> You can't, in general, close *all* open file descriptors. OPEN_MAX
> may not exist (and I would guess that it doesn't on the HURD). It's
> completely reasonable for a daemon to that doesn't open any extras to
> assume that only std
On 11-Jan-02, 08:45 (CST), "Stefan Hornburg (Racke)" <[EMAIL PROTECTED]> wrote:
> Yeah, but it is really a bug that should be filed. The daemon will
> be killed by SAK otherwise (look at #92277 for further enlightenment).
You can't, in general, close *all* open file descriptors. OPEN_MAX
may not
On Fri, 11 Jan 2002, Wichert Akkerman wrote:
> Previously Henrique de Moraes Holschuh wrote:
> > On Fri, 11 Jan 2002, Michael Meskes wrote:
> > > In quota.postinst rpc.quotad is started using start-stop-daemon. This
> > > works
> >
> > Don't, please. This will be forbidden in the future (right no
Previously Henrique de Moraes Holschuh wrote:
> On Fri, 11 Jan 2002, Michael Meskes wrote:
> > In quota.postinst rpc.quotad is started using start-stop-daemon. This works
>
> Don't, please. This will be forbidden in the future (right now this is ok),
> you should use the /etc/init.d interface.
Wh
On Fri, Jan 11, 2002 at 09:45:22AM -0500, Stefan Hornburg (Racke) wrote:
> Mark Brown <[EMAIL PROTECTED]> writes:
> > Or has called the standard daemon() function which doesn't close all the
> > file descriptors.
> Yeah, but it is really a bug that should be filed. The daemon will
> be killed by
Mark Brown <[EMAIL PROTECTED]> writes:
> On Fri, Jan 11, 2002 at 11:40:28AM -0200, Henrique de Moraes Holschuh wrote:
>
> > Ah, it looks like you need to have a db_stop BEFORE you call
> > start-stop-daemon or the initscript. Looks like the daemon is dumb and does
>
> No, the ordering is unimpor
On Fri, Jan 11, 2002 at 11:40:28AM -0200, Henrique de Moraes Holschuh wrote:
> Don't, please. This will be forbidden in the future (right now this is ok),
> you should use the /etc/init.d interface. If you need extra functionality,
Sorry, I wasn't precies enough. It does call /etc/init.d/quotarpc
On Fri, Jan 11, 2002 at 11:40:28AM -0200, Henrique de Moraes Holschuh wrote:
> Ah, it looks like you need to have a db_stop BEFORE you call
> start-stop-daemon or the initscript. Looks like the daemon is dumb and does
No, the ordering is unimportant. db_stop stops debconf no matter when
you call
On Fri, 11 Jan 2002, Michael Meskes wrote:
> In quota.postinst rpc.quotad is started using start-stop-daemon. This works
Don't, please. This will be forbidden in the future (right now this is ok),
you should use the /etc/init.d interface. If you need extra functionality,
you should request the mai
On Fri, Jan 11, 2002 at 01:04:25PM +0100, Petter Reinholdtsen wrote:
> [Mark Brown]
> > You need to explicitly end Debconf processing in the postinst by
> > calling db_stop. debconf causes child processes to have an extra
> > file descriptor open and waits for these to be closed before exiting
> >
On Fri, Jan 11, 2002 at 01:04:25PM +0100, Petter Reinholdtsen wrote:
> Is this the case for all postinst scripts? db_stop is not mentioned
> in my /usr/share/doc/debconf-doc/tutorial.html, which I use as my
> debconf reference.
No. If your postinst does not leave processes running then there wo
On Fri, Jan 11, 2002 at 11:58:47AM +, Mark Brown wrote:
> You need to explicitly end Debconf processing in the postinst by calling
That's it. Thanks a lot.
Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
pgpfJMEeIzDdh.pgp
D
[Mark Brown]
> You need to explicitly end Debconf processing in the postinst by
> calling db_stop. debconf causes child processes to have an extra
> file descriptor open and waits for these to be closed before exiting
> and the daemon doesn't know it has this file open so doesn't close
> it.
Is
On Fri, Jan 11, 2002 at 12:44:39PM +0100, Michael Meskes wrote:
> In quota.postinst rpc.quotad is started using start-stop-daemon. This works
> as longs as I know the package. Now it doesn't anymore. That is the daemon
> is correctly started but quota.postinst does not return anymore. It remains
>
I'm currently working on adding debconf to quota. Well in fact Torsten
Lnadschoff did that and send me the patch. However, during my tests I found
a strange problem.
In quota.postinst rpc.quotad is started using start-stop-daemon. This works
as longs as I know the package. Now it doesn't anymore.
20 matches
Mail list logo
