PDA

View Full Version : Error in starting up a daemon




Jose Jayan
Jun 22, 2009, 03:36 AM
Hi there

Error while trying to start a daemon from the following sample
http://developer.apple.com/samplecode/SampleD/index.html

Error:
launchctl: Dubious ownership on file (skipping): ./com.apple.dts.SampleD.plist
nothing found to load

Thanks in advance,
Jose



cqexbesd
Jun 22, 2009, 05:31 AM
Error:
launchctl: Dubious ownership on file (skipping): ./com.apple.dts.SampleD.plist
nothing found to load

Base don nothing but the error message... have you checked the ownership of the plist file? "ls -l" from the command line and compare to the other files.

HTH,

Andrew

lee1210
Jun 22, 2009, 08:25 AM
The file should have permissions 644, and belong to the user it is to be launched as.

If there are write permissions for others, this means that someone else on the system could change something that's being run automatically, which could just be a script that erases your home directory.

-Lee

Jose Jayan
Jun 23, 2009, 12:31 AM
Hi

The permission on the plist file is:

-rw-r--r--@ 1 defaultuser staff

where defaultuser is the current logged in user.

Command:
"sudo launchctl load ./com.apple.dts.SampleD.plist"

Error:
Password:
launchctl: Dubious ownership on file (skipping): ./com.apple.dts.SampleD.plist
nothing found to load

Thanks
J

Jose Jayan
Jun 23, 2009, 12:32 AM
Tanx in advance

larkost
Jun 23, 2009, 12:50 AM
Look at the permissions/owner/group of the other items in that folder. Make it match those permissions/owner/group. The error message is telling you what to look at.

Jose Jayan
Jun 25, 2009, 03:08 AM
Hi

I have tried setting various permissions levels for the plist file.
Still bad luck.
Any idea?

OS:
Mac OS X 10.5.7

Thx
Jose

cqexbesd
Jun 25, 2009, 06:11 AM
I have tried setting various permissions levels for the plist file.
Still bad luck.
Any idea?


Perhaps you should post the output of ls -l in that directory, and the contents of the plist, and someone might be able to spot what is wrong. I haven't got a mac here to check.

As someone else said the file probably has to be owned by the person trying to start it. Who is running launchctl?