problem with dhcpd and daemondo

Ryan Schmidt ryandesign at macports.org
Wed Oct 17 13:35:05 PDT 2007


On Oct 17, 2007, at 14:47, BB wrote:

> Problem solved and now I want to know how to fix the portfile. But
> first let me explain the solution.
>
> I found this thread:
> http://lists.macosforge.org/pipermail/macports-users/2007-June/ 
> 004009.html
>
> And changed /Library/LaunchDaemons/org.macports.dhcpd.plist from:
>
>         <key>ProgramArguments</key>
>         <array>
>                 <string>/opt/local/bin/daemondo</string>
>                 <string>--label=dhcpd</string>
>                 <string>--start-cmd</string>
>
> to this:
>
>         <key>ProgramArguments</key>
>         <array>
>                 <string>/opt/local/bin/daemondo</string>
>                 <string>--label=dhcpd</string>
>                 <string>--restart-netchange</string>
>                 <string>--start-cmd</string>
>
> Rebooted and that solved the problem. I'm guessing that Mac mini G4
> was slower and therefore the race condition was never met and it
> worked on the older/slower Mac mini.
>
> As I rely on dhcpd my question is now how can the portfile be fixed?

See two messages later in that thread:

http://lists.macosforge.org/pipermail/macports-users/2007-June/ 
004011.html

On Thu Jun 21 15:34:14 PDT 2007 James Berry wrote:

> Well, currently we don't have any easy way to put that change into
> the portfile itself, and have it reflected down into the generated
> plist. Granted, we should. It's likely that the illustrated line
> would be useful in most networked daemons.

I'm not sure if a bug is filed in Trac. If not, you could file it and  
point back at this and the previous mail threads. Patches to MacPorts  
base would of course be welcome as well.




More information about the macports-users mailing list