I have a launchd on-demand job that is triggered on network access. The plist looks like this: <dict> <key>Label</key> <string>com.kulakov.vm.development</string> <key>ProgramArguments</key> <array>_omitted_</array> <key>inetdCompatibility</key> <dict> <key>Wait</key> <false/> </dict> <key>Sockets</key> <dict> <key>NetworkListener</key> <dict> <key>SockServiceName</key> <string>5906</string> <key>SockType</key> <string>stream</string> </dict> </dict> </dict> </plist> The program is essentially a bash script that looks like this: #!/bin/bash nc -w 300 some_ip 5907 At this point, I expect that when a packet comes to the 5906, tcp proxy using nc will be started and the job keep running until nc returns. Unfortunately the job is killed before nc returns. When new connection is made to 5906, the script is restarted. Is it intended to work like this? -- View this message in context: http://mac-os-forge.2317878.n4.nabble.com/Job-is-terminated-before-the-daemo... Sent from the Launchd mailing list archive at Nabble.com.