>
> Ah. Nothing was mentioned about that before. Bad news - starting it
> doesn't seem to make any difference so far. I've tried starting it with and
> without a sudo, it doesn't make any complaints but checking the status
> return either 0 seconds or 1 second, which makes it seem it isn't feeling
> too happy. But there isn't any log for the log logger log...
>

Heh, that's funny.  :)  Recall, daemontools simply runs the "run" script in
the service directory, so what happens if you try running it in the
foreground tty?

   sudo ./log/run

> From your image directory, you could try a sudo setuidgid pi echo test >
> './log/main/test.out'  and see if you get any revealing error messages?
>
> That works fine, which I hope means permissions are ok


Not necessarily the execute permission needed on log/run.


> One bit of weird is the way I ended up with
> /service -> /etc/service
> /etc/service contains
>    service -> /etc/service
>   ss -> /home/pi/SqSrcDeploy/ss
>   supervise
>
> It's hard to imagine requiring a link to yourself in a directory? I can't
> see any way it would get created in your deployment scripts. Deleting it
> doesn't appear to make any difference though.
>

I think daemontools makes that, no idea why.  I deleted mine, too.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20190911/c7d26a32/attachment.html>