[MacPorts] #42347: dbus: launchctl: Couldn't stat /System/Library/LaunchDaemons/com.apple.DirectoryServicesLocal.plist
MacPorts
noreply at macports.org
Wed Feb 5 07:47:18 PST 2014
#42347: dbus: launchctl: Couldn't stat
/System/Library/LaunchDaemons/com.apple.DirectoryServicesLocal.plist
---------------------------------+------------------------
Reporter: j.orlandomurillo@… | Owner: jeremyhu@…
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: | Keywords:
Port: dbus |
---------------------------------+------------------------
Comment (by cal@…):
Replying to [comment:20 j.orlandomurillo@…]:
> I applied the patch you provided, reinstalled dbus, and it worked.
Great, thanks for testing! I'll commit the patch and it'll be released
with MacPorts 2.3 then.
> What does that patch do exactly
To create new system users, MacPorts executes `dscl`, a low-level tool
provided by OS X to manage users. To execute this tool, MacPorts uses the
Tcl function `exec`, which normally considers the execution of a tool to
have failed, if the tool prints any output to stderr. My patch improves
the error handling of user creation and avoids `exec` to cause an error
when `dscl` prints a message to stderr.
> why didn't the dbus installation affect my other computers?
Because your other computers don't print `launchctl: Couldn't
stat("/System/Library/LaunchDaemons/com.apple.DirectoryServicesLocal.plist"):
No such file or directory` on stderr when executing `dscl`. As to why your
other computers don't print this (or rather, why one of them does), I have
no idea. `dscl` is an Apple tool that we're merely using and I don't know
enough about its internals to be able to diagnose why it prints this
(apparently harmless) message. I suppose this could be considered a bug in
`dscl` and should be filed with Apple.
--
Ticket URL: <https://trac.macports.org/ticket/42347#comment:21>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list