Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38930 - [munin] No [Install] section in munin-graph.service and munin-html.service

Attached to Project: Arch Linux
Opened by Dark (Dark) - Sunday, 16 February 2014, 01:50 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Sunday, 16 February 2014, 14:26 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

As per title, munin-graph.service and munin-html.service (for cgi graphs and html respectively) can only be started, not installed for auto-running on boot.

It's possible that I am misunderstanding the usage of these services (are they supposed to be called by something else?)
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Sunday, 16 February 2014, 14:26 GMT
Reason for closing:  Not a bug
Comment by Dan McGee (toofishes) - Sunday, 16 February 2014, 02:07 GMT
They both have respective .socket files and are meant to be socket-activated, not explicitly started or installed.
Comment by Dark (Dark) - Sunday, 16 February 2014, 02:10 GMT
Ah that makes more sense, sorry for the redundant bug report!
Comment by Dave Reisner (falconindy) - Sunday, 16 February 2014, 02:11 GMT
You're meant to enable the socket, not the service. Note that you can't really start these services either, because they require stdin/stdout to be a connected socket.

One could add an [Install] section to the services with "Also=munin-graph.socket" (or -html) so that the socket is enabled for you.
Comment by Dark (Dark) - Sunday, 16 February 2014, 02:13 GMT
Cheers, I think I've got it figured out now. I was thrown by the fact that starting the services worked, didn't think .socket files were anything to do with services

Learn something new every day :)

Loading...