[MacPorts] #14163: Endless Avahi system.log errors

[Ryan Schmidt]

Le 3 févr. 08 à 19:15, Adam Dershowitz a écrit :

> I have looked into this a little more.  I am not sure, but it looks  
> to me like org.macports.dbus.plist is disabled by default (at least  
> when this problem cropped up, I was showing it as disabled, so I  
> assume it started that way....or something else changed it).  In  
> other words the launchd flag in the plist is set to true for  
> disabled.  While the avahi-dnsconfd and avahi-daemon launchd are  
> set to enabled (well actually disabled is false).
> I googled around some and found that dbus port should say this  
> during the install (although I didn't notice it at the time):
>
> --->  Creating launchd control script
> ###########################################################
> # A startup item has been generated that will aid in
> # starting dbus with launchd. It is disabled
> # by default. Execute the following command to start it,
> # and to cause it to launch at startup:
> #
> # sudo launchctl load -w /Library/LaunchDaemons/ 
> org.macports.dbus.plist
> ###########################################################
>
> As I understand it a bunch of launchd stuff is not reconfigured  
> until a restart of the machine.

Which part of launchd do you think requires a restart? I thought that  
one of the advantages of launchd over startupitems was that with  
launchd you can start and stop services immediately rather than wait  
for a restart which you had to do with startupitems.

> So the problem could be just that dbus is disabled and avahi is  
> enabled by default.  And, if that is the case, we probably need a  
> Macports policy to make these things consistent since one depends  
> on the other one.
> Does this make sense, and look likely to you?
>
> Thanks for handing this port and looking into this problem.  It  
> could be a somewhat insidious problem as it only cropped up when I  
> did a reboot, which doesn't happen that often.