Hot answers tagged launchctl
I found the solution sudo launchctl log level debug and after this tail -f /var/log/system.log
It is the last exit code of that service. The launchctl man page describes it. list [-x] [label] With no arguments, list all of the jobs loaded into launchd in three columns. The first column displays the PID of the job if it is running. The second column displays the last exit status of the job. If the number in ...
assuming you're trying to log your process rather than launchd itself, if you include the following lines in the launchd plist file: <key>StandardOutPath</key> <string>/path/to/logfile.log</string> <key>StandardErrorPath</key> <string>/path/to/another_logfile.log</string> and reload the process, any logging ...
Hmm, maybe this helps to debug your issue: Set the log level to debug: sudo launchctl log level debug Tail the system.log: sudo tail -f /var/log/system.log & Try to start your job again: sudo launchctl start org.job-label
You can kill the mysql process manually. $ ps ax | grep mysql Note the process id. Then, $ kill __pid__ Next thing you should do is edit your my.cnf file, and check to make sure that the socket location is /tmp/mysql.sock. For example, this is what my [client] section looks like: [client] user=mysql port=3306 socket=/tmp/mysql.sock Let's say $MYSQL ...
Finder is a LaunchAgent, not a LaunchDaemon, which means it's loaded as part of your login session. Either use launchctl unload without sudo, or just log out & back in.
php-fpm's error code 78 seems to correspond to EX_CONFIG (see one of the messages here), indicating some sort of configuration error. It's possible the error is preventing php-fpm from using any of your configured settings, including logging settings. You may be able to get more information by capturing the stdin and stdout from the php-fpm process by adding ...
Use WorkingDirectory option: WorkingDirectory <string> This optional key is used to specify a directory to chdir(2) to before running the job. To see all available options, check launchd.plist manual page.
This is intended behavior. Issuing launchctl stop for a job which has not been loaded does not work.
1. ulimit This is a builtin command of your shell (bash/ash/zsh etc). It temporarily sets process limits for the current shell. This is not OS X specific by the way. 2. sysctl Most unix-like (Linux/*BSD/OS X) systems set global limit/kernel settings via the sysctl command//etc/sysctl.conf config file. But see below for the OS X caveat. 3. launchd Seems ...
System Mac OS X, version: 10.6.8 (Snow Leopard) Task I wanted to prohibit, mostly the initial auto-starting but also, the automatic re-launching of the Finder (as a "simple" fix for decrypting encrypted disks) before the Finder would try (and fail) to load (and in that process discard) it's old (preferences'd) list of previous open locations.. Reliability ...
As Gordon said, you need to execute your launchctl unload ... command in the same mach bootstrap context of the user. launchctl itself has a facility to do this via bsexec, you just need to provide it a PID of any process running in that user context, Finder isn't running so pick a different one. The user-relative root process is loginwindow console, so this ...
Your log shows that Finder is being run for user 502, but you are running launchctl with sudo, and root isn't running a Finder. Try the launchctl unload without sudo.
Only top voted, non community-wiki answers of a minimum length are eligible