Thank you Colin. First I made mistake not to make properly the directories, and then the file dependencies was there empty. When I remove the file, it started working.
Jean On Sat, Jul 22, 2017 at 10:21:52PM +0000, Colin Booth wrote: > On Sat, Jul 22, 2017 at 12:52:45PM +0300, Jean Louis wrote: > > Hello, > > > > I have these files: > > > > ~/Programming/services/cron > > > > cron/run: executable > > > > #!/bin/execlineb -P > > /home/data1/protected/bin/lisp > > /home/data1/protected/Programming/git/RCDBusiness/lib/lisp/cron/cron.lisp > > > > cron/type: > > longrun > Not actually necessary unless you're using s6-rc. ./type files are used > in the pre-compiled s6-rc source to tell s6-rc-compile how to treat a > service. The base s6 supervisory system ignores those files. > > > > > > and I can run s6-svscan in the dir just fine. But > > it does not run the ./run file. > Are you running s6-svscan against ~/Programming/services/ or > ~/Programming/services/cron? If you're doing the latter it won't work > because s6-svscan expects to see service dirs within its target. > > > > It is all in user space. If I run ./run from > > command line, it works. > > > > What do I miss? > I'm guessing an incorrect target for s6-svscan, but you'll have to > answer that for me. > > > > Jean > Cheers! > -Colin