> -----Original Message----- > From: Jacob Kjome [mailto:[EMAIL PROTECTED] > > I'm trying to set --WorkingPath in service.bat, but it doesn't seem to do > anything. It used to in Tomcat-5.0.19 but doesn't in Tomcat-5.0.24. Is > there a > new property to set the working path for the service? I also tried adding > the > property PR_WORKINGPATH, but that didn't do anything either. > > Now, I know that I can bring up the gui and set it manually, but my > requirement > is to set it in the script so no manipulation of the gui is necessary. >
Use the --StartPath and --StopPath. Those are the working paths for startup or shutdown processes, and are used to set the custom working paths.
Thanks for the info
The preferred way of running TC since 5.0.19 is using jni, so you don't need them.
Hmm... Can you explain a bit more? What does using jni have to do with a working path? How does using jni result in not requiring a working path? If I used jni as you say, and I created a new File("testfile.txt") and wrote it, where would it go? If I had a working path set, I'd expect this to show up at the location of the working path or, if none is specified, whatever directory the VM started from. If you can clarify this, it would be very helpful.
Oh, one other question. How does one specify that the service should be able interact with the desktop? That is, again, in service.bat, not manually via the gui.
> BTW, it would be *really* nice if the docs were updated to show all the > properties available. The commons-daemon procrun site ( > http://jakarta.apache.org/commons/daemon/procrun.html ) hasn't been > updated > since January 13. >
You are right about that. Lack of time I'm afraid.
I know the feeling.
Jake
MT.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
