Hi folks,
I have the impression that sometimes invoke-rc.d fails to
restart services with children, e.g. zabbix-agent, sssd or
opensmtpd. The service and its children are stopped, but
not started again. Looking at "simple" services (without
children) there is no such problem.
It app
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 *ol
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 b
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 accou
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-pack
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 in
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
That might behave different than expected when current state of the
daemon and the boot configuration differ: for example the sequen
t; 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
That works, but it doesn't take into account any socket activation or
other such functionality (whic
run invoke-rc.d daemon-package stop
2. update config file
3. run invoke-rc.d daemon-package start
Thanks in advance.
--
André Majorel <http://www.teaser.fr/~amajorel/>
Dear spammer : the email addresses in this message have been
brought to you by bugs.debian.org.
Hi all,
I am running into this issue, there is the solution.
Just for archival purpose.
http://sidux.com/PNphpBB2-viewtopic-t-18679-view-previous.html
--
Architecte Informatique chez Blueline/Gulfsat:
Administration Systeme, Recherche & Developpement
+
>
> >> > I get the above error message whenever I use invoke-rc.d. This
> isn't a
> >> > major problem except that I get annoying messages every night when
> logrotate
> >> > restarts services. Is there a fix for this?
> >&
On Sun, Jun 28, 2009 at 10:28 PM, Robert
S wrote:
>> > I get the above error message whenever I use invoke-rc.d. This isn't a
>> > major problem except that I get annoying messages every night when
>> > logrotate
>> > restarts services. Is there a fi
>
> > I get the above error message whenever I use invoke-rc.d. This isn't a
> major problem except that I get annoying messages every night when logrotate
> restarts services. Is there a fix for this?
> >
> > # invoke-rc
On Sat, Jun 27, 2009 at 7:16 PM, Robert S
wrote:
>
> I get the above error message whenever I use invoke-rc.d. This isn't a major
> problem except that I get annoying messages every night when logrotate
> restarts services. Is there a fix for this?
>
> # invoke-rc.d
I get the above error message whenever I use invoke-rc.d. This isn't a
major problem except that I get annoying messages every night when logrotate
restarts services. Is there a fix for this?
# invoke-rc.d samba restart
invoke-rc.d:
i
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
&
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.
>
hello,
time sudo invoke-rc.d dictd stop
real0m30.055s
user0m0.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 upgrade in sid.
--
Gérard
Hello Will!
On Sat, Apr 17, 2004 at 09:30:50PM -0500, Will Trillich wrote:
> On Sat, Apr 17, 2004 at 04:13:54PM -, Monique Y. Mudama wrote:
> > what about invoke-rc.d ?
>
> aha! perfect!
>
> i've been using debian since 1997 or so, and until four minutes
>
> service
> >
> > which runs /etc/init.d/* scripts. how come woody doesn't have such a
> > thing by default? i'm wondering if there's a security issue that isn't
> > obvious to the neophyte...?
>
> what about invoke-rc.d ?
aha! perfect!
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
.
After unpacking 0B of additional disk space will be used.
Setting up apache (1.3.29.0.2-4) ...
Starting web server: apache failed
invoke-rc.d: initscript apache, action "start" failed.
dpkg: error processing apache (--configure):
subprocess post-installation script returned error exit statu
Kevin Mark <[EMAIL PROTECTED]> writes:
> You can see what script is failing by looking in
> /var/lib/dpkg/info/.* Although, it seems that the prerm
> (pre-remove) script is trying to shut down alsa by running
> /etc/init.d/alsa stop (may no be correct name). So, you may need to
> do a workaround b
g 2879kB disk space will be freed.
> Do you want to continue? [Y/n] y
> (Reading database ... 269782 files and directories currently installed.)
> Removing alsa-modules-2.4.22-1-386 ...
> Storing ALSA mixer settings ... failed
> Shutting down ALSA (version 0.9.6): aborting. (sound
...
Storing ALSA mixer settings ... failed
Shutting down ALSA (version 0.9.6): aborting. (sound used by PIDs 702
849)
invoke-rc.d: initscript alsa, action "stop" failed.
dpkg: error processing alsa-modules-2.4.22-1-386 (--remove):
subprocess post-removal script returned error exit status 1
E
27 matches
Mail list logo
