On Sun, Aug 07, 2016 at 03:58:50PM +0200, Andre Majorel wrote:
> What is a "socket activation" ? Would that by any chance be a
> systemd thing to declare that you plan to listen on some port ?
It is also possible via various inetd solutions.
--
Jonathan Dowland
Please do not CC me, I am subscrib
André Majorel:
Do you think the following would work on any Debian system, regardless
of its current run level and choice of init system ?
1. run invoke-rc.d daemon-package stop
2. update config file
3. run invoke-rc.d daemon-package start
Don't use invoke-rc.d yourself. The *old pre-system
Henrique de Moraes Holschuh writes:
> On Sun, 07 Aug 2016, Ansgar Burchardt wrote:
>> That might behave different than expected when current state of the
>> daemon and the boot configuration differ: for example the sequence above
>
> It shouldn't, unless invoke-rc.d is broken.
It does as you say y
On Sun, 07 Aug 2016, Ansgar Burchardt wrote:
> That might behave different than expected when current state of the
> daemon and the boot configuration differ: for example the sequence above
It shouldn't, unless invoke-rc.d is broken. The whole reason it exists
is exactly to account for boot state
On Sun, 07 Aug 2016, Andre Majorel wrote:
> On 2016-08-07 10:19 -0300, Henrique de Moraes Holschuh wrote:
> > On Sun, 07 Aug 2016, Andre Majorel wrote:
> > > 1. run invoke-rc.d daemon-package stop
> > > 2. update config file
> > > 3. run invoke-rc.d daemon-package start
> >
> > That works, but it d
On 2016-08-07 10:19 -0300, Henrique de Moraes Holschuh wrote:
> On Sun, 07 Aug 2016, Andre Majorel wrote:
>
> > 1. run invoke-rc.d daemon-package stop
> > 2. update config file
> > 3. run invoke-rc.d daemon-package start
>
> That works, but it doesn't take into account any socket activation or
> ot
Andre Majorel writes:
> I'm working on a program to make changes to a daemon's
> configuration file. The man page helpfully warns against doing
> that without immediately restarting it.
>
> Do you think the following would work on any Debian system,
> regardless of its current run level and choice
On Sun, 07 Aug 2016, Andre Majorel wrote:
> I'm working on a program to make changes to a daemon's
> configuration file. The man page helpfully warns against doing
> that without immediately restarting it.
>
> Do you think the following would work on any Debian system,
> regardless of its current
On Tue, Jan 22, 2008 at 08:33:01PM +0100, Sven Joachim wrote:
From: Sven Joachim <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: Re: "invoke-rc.d dictd stop" gets long time.
Mail-Followup-To: debian-user@lists.debian.org
X-Spam-Virus: No
X-Spam-Checker-Version: Sp
On Tue, 22 Jan 2008 20:04:09 +0100
Gerard Robin <[EMAIL PROTECTED]> wrote:
> hello,
>
> time sudo invoke-rc.d dictd stop
>
> real 0m30.055s
> user 0m0.024s
> sys 0m0.028s
>
> The same problem arises when I shutdown my box to stop all the services and
> the
> machine stops after a very long
On 2008-01-22 20:04 +0100, Gerard Robin wrote:
> time sudo invoke-rc.d dictd stop
>
> real 0m30.055s
> user 0m0.024s
> sys 0m0.028s
>
> The same problem arises when I shutdown my box to stop all the services and
> the
> machine stops after a very long time.
>
> This happens after a recent upg
Hello 'nameless'!
On Thu, Apr 01, 2004 at 04:07:46PM +, [EMAIL PROTECTED] wrote:
> Has anyone been able to duplicate (and correct) this problem? It seems I'm
Other people exerience the very same error, please see
http://bugs.debian.org/239416
> now having the same problem and NEED to get the
12 matches
Mail list logo