Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm setting up a Hudson build slave on an OS X machine. I'm using launchd to start the slave using the following plist in `/Library/LaunchDaemons/':

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
<plist version="1.0">

I'm currently putting the slave.jar and slave-agent.jnlp files in /Users/Shared/Hudson but this seems like an unnecessarily user-visible location. What's the convention? Where should I be putting these JARs for a daemon?

share|improve this question

Where Do Apps usually write their data? How about the home directory of the user, that the slave runs under?

I have question regarding the slave.jar. Isn't the most current version of the slave.jar downloaded when executing the jnlp file?

share|improve this answer
Peter, on OS X, the launchd daemon runs the process, but does not have a home folder. GUI (Cocoa) apps use /Library/Application Support/[]/, but I don't know if this is the best answer for this situation (hence the question). – Barry Wark Nov 24 '10 at 23:42
javaws would download the Jar, but cannot run headless. In this case, we use java -jar slave.jar -jnlpUrl ... so that it can run headless. – Barry Wark Nov 24 '10 at 23:43
A Apple developer page states: "It is also possible to run additional copies of launchd, most often run by a non-root user. When non-root users load jobs, the launchd daemon handling their jobs runs with their non-root privileges, giving an extra layer of security." I would strongly recommend to you not running it under root. So the user that launchd runs under (lets say Hudson) can have a Home directory that is used for all the Hudson files. Work;s like a charm for me. -- see – Peter Schuetze Nov 29 '10 at 17:31
Regarding javaws. You confused me, because you copy the jnlp file, which in your case is completely unnecessary. Did you think about launching the SSL client via SSH? Pros: less configuration issues, slave can be launched on demand, you will always have the newest slave.jar – Peter Schuetze Nov 29 '10 at 17:43

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.