[MacPorts] #32138: dnsmasq @2.59_1 does not respect it's own notes
#32138: dnsmasq @2.59_1 does not respect it's own notes --------------------------------------+------------------------------------- Reporter: nonstop.server@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: net | Port: dnsmasq --------------------------------------+------------------------------------- The notes for port dnsmasq state: {{{ dnsmasq has the following notes: A startup item has been generated that will aid in starting dnsmasq with launchd. You must specify the path to resolv.conf. For your protection, this script is disabled by default. Execute the following command to start it, and to cause it to launch at startup: sudo port load dnsmasq }}} However after a successfull installation or upgrade of dnsmasq the startup item gets loaded regardless of entering the load command.[[BR]] The startup item gets loaded under the launched of user root after the first reboot of the system when dnsmasq is installed or upgraded.[[BR]] [[BR]] As workaround one could immediately disable dnsmasqs startup item after first reboot using the unload command. {{{ sudo port unload dnsmasq }}} The startup item will stay disabled until it gets loaded trough the load command. -- Ticket URL: <https://trac.macports.org/ticket/32138> MacPorts <http://www.macports.org/> Ports system for Mac OS
#32138: dnsmasq @2.59_1 does not respect it's own notes --------------------------------------+------------------------------------- Reporter: nonstop.server@… | Owner: snc@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: dnsmasq --------------------------------------+------------------------------------- Changes (by snc@…): * owner: macports-tickets@… => snc@… * keywords: net => * version: 2.0.3 => * status: new => assigned -- Ticket URL: <https://trac.macports.org/ticket/32138#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#32138: dnsmasq @2.59_1 does not respect it's own notes --------------------------------------+------------------------------------- Reporter: nonstop.server@… | Owner: snc@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: dnsmasq --------------------------------------+------------------------------------- Changes (by ryandesign@…): * cc: snc@… (removed) Comment: Replying to [ticket:32138 nonstop.server@…]:
However after a successfull installation or upgrade of dnsmasq the startup item gets loaded regardless of entering the load command.[[BR]] The startup item gets loaded under the launched of user root after the first reboot of the system when dnsmasq is installed or upgraded.
That's not how launchd works, based on my understanding, so I can't explain why that's happening for you. But I also haven't tested it myself. -- Ticket URL: <https://trac.macports.org/ticket/32138#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#32138: dnsmasq @2.59_1 does not respect it's own notes --------------------------------------+------------------------------------- Reporter: nonstop.server@… | Owner: snc@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: dnsmasq --------------------------------------+------------------------------------- Comment(by nonstop.server@…): Replying to [comment:2 ryandesign@…]:
Replying to [ticket:32138 nonstop.server@…]:
However after a successfull installation or upgrade of dnsmasq the startup item gets loaded regardless of entering the load command.[[BR]] The startup item gets loaded under the launched of user root after the first reboot of the system when dnsmasq is installed or upgraded.
That's not how launchd works, based on my understanding, so I can't explain why that's happening for you. But I also haven't tested it myself. This is the only installed port with a startup item on my system which has this behavior.[[BR]] There is a difference with ports like denyhosts or rsync, which also use a startup item that only gets loaded after the user issues the load command.[[BR]] Those two ports use a daemondo wrapper along with a launchd.plist and this works as the creation message of the launch control script states at installation.[[BR]] Except for the difference in using a daemondo support script I'm unable to come up with a reason why this is happening.
-- Ticket URL: <https://trac.macports.org/ticket/32138#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#32138: dnsmasq @2.59_1 does not respect it's own notes ---------------------------------------+------------------------------------ Reporter: nonstop.server@… | Owner: snc@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: dnsmasq | ---------------------------------------+------------------------------------ Changes (by snc@…): * status: assigned => closed * resolution: => fixed Comment: Launchd item is now disabled by default, r87682. -- Ticket URL: <https://trac.macports.org/ticket/32138#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts