On Mon, Mar 13, 2017 at 04:44:41AM +0100, Benoît-Pierre Demaine wrote:
> Because in Unix most services are enabled or disabled via classic commands
> /etc/init.d/foo start, or handling links in rc3.d. messing cron files is
> counter intuitive.
using "/etc/init.d/foo start" has been deprecated s
Because in Unix most services are enabled or disabled via classic commands
/etc/init.d/foo start, or handling links in rc3.d. messing cron files is
counter intuitive.
Systems replaces init.d and rc3.d with systemctl. Good. Init.d/munin never
existed, and was never needed in the past, why did yo
control: tags -1 moreinfo
control: severity -1 normal
thanks
On Sat, Mar 11, 2017 at 07:46:29PM +0100, Andreas Henriksson wrote:
> No, there's no need for a service file since it's already implemented
> in a much better way:
>
> https://sources.debian.net/src/munin/2.0.33-1/debian/munin-common.tm
On Sat, Mar 11, 2017 at 11:04:25AM +, Holger Levsen wrote:
[...]
> however, all that /etc/init.d/munin really does, is "mkdir && chown
> /var/run/munin".
>
> that's all we need as a service file to fix this bug. Pretty trivial. Still,
> help welcome.
[...]
No, there's no need for a service f
On Sat, Mar 11, 2017 at 10:31:03AM +0100, Benoît-Pierre DEMAINE wrote:
> In fact, before systemd, munin (server) did not need init script at all;
it did.
however, all that /etc/init.d/munin really does, is "mkdir && chown
/var/run/munin".
that's all we need as a service file to fix this bug. P
On 11/03/17 02:33, Matthew Gabeler-Lee wrote:
> On Fri, 10 Mar 2017, Simon McVittie wrote:
>
>> However, Matthew Gabeler-Lee's reply:
>>
>>> I argue this merits worse than "important" -- in a default install of
>>> Stretch currently, munin doesn't work at all.
>>
>> suggests that there may be somet
On Fri, 10 Mar 2017, Simon McVittie wrote:
However, Matthew Gabeler-Lee's reply:
I argue this merits worse than "important" -- in a default install of
Stretch currently, munin doesn't work at all.
suggests that there may be something else going on.
Matthew, please could you describe what yo
Control: tags 837788 + moreinfo
On Fri, 10 Mar 2017 at 07:46:17 +0100, Stig Sandbeck Mathisen wrote:
> Munin needs /run/munin created with the correct permissions.
>
> When using sysv init, the /etc/init.d/munin script does that, and exits.
Aha. So the boot process (systemd or sysvinit) in jessi
Simon McVittie writes:
> Well, you're the maintainer; if you want munin to not mask the systemd
> unit generated from its init script, you don't have to install that
> symlink. It seems to have been done deliberately:
> https://sources.debian.net/src/munin/2.0.33-1/debian/munin.links/ Do
> you k
On Thu, 09 Mar 2017 at 10:37:10 +, Holger Levsen wrote:
> On Wed, Mar 08, 2017 at 09:45:32PM -0500, Matthew Gabeler-Lee wrote:
> > This takes it back to using the sysvinit script with systemd. I don't know
> > if this might cause difficulties with future upgrades, but it at least gets
> > muni
control: severity -1 serious
control: tags -1 + help
thanks
Hi Matthew,
On Wed, Mar 08, 2017 at 09:45:32PM -0500, Matthew Gabeler-Lee wrote:
> I argue this merits worse than "important" -- in a default install of
> Stretch currently, munin doesn't work at all.
ouch. thanks for pointing this out
Package: munin
Version: 2.0.33-1
Followup-For: Bug #837788
I argue this merits worse than "important" -- in a default install of
Stretch currently, munin doesn't work at all.
Also worthy of note is this workaround:
sudo rm /lib/systemd/system/munin.service
sudo systemctl enable munin
sudo systemc
control: severity -1 important
On Wed, Sep 14, 2016 at 05:37:52PM +0200, Dieter Adriaenssens wrote:
> It seems the systemd control scripts are missing for this package.
> #systemctl restart munin.service
> gives this error message :
> Failed to restart munin.service: Unit munin.service is masked.
Package: munin
Version: 2.0.25-1
Severity: normal
Dear Maintainer,
It seems the systemd control scripts are missing for this package.
#systemctl restart munin.service
gives this error message :
Failed to restart munin.service: Unit munin.service is masked.
Init style scripts work fine (/etc/i
14 matches
Mail list logo
