Well, for one thing, svc never created the supervise directory. Maybe for instance the run file doesn't have the right permissions or something. But one thing is for sure, Michael is getting a lot of advice, but not giving much information to help us out in diagnosing the problem. What is in the run file? Never said. Permissions? Who knows. Also, there is a log directory in the same directory as the run file. This usually creates a problem with svc, because it wants to create a second supervise process there. Maybe it is looking for the log/run file, and can't find that.
What I do is to create a directory structure like this:
/web
/web/oacs
/web/control
/web/control/oacs
/web/control/oacs/serverlog
/web/control/oacs/accesslog
;; then
ln -s /web/control/oacs /service
One thing I am not clear on is how Michael linked the oacs directory in and yet, daemontools didn't auto-start the web service? Maybe svscan isn't even running? No info on that either, although asked for yesterday.
