runsvdir does not run runsv recursively, as is documented.

runsvdir does not run runsv recursively, as is documented.

[Martin Castillo]

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]

Hi,

I'm trying to set up services, which are in subdirectories of other 
services. This is supported, according to the second paragraph of the 
runsvdir man page:

runsvdir starts a runsv(8) process for each subdirectory,  or
symlink  to a directory, in the services directory dir, up to
a limit of  1000  subdirectories,

In my directory service/ I have:
Foo
Foo/run
Foo/bar
Foo/bar/run

After running runsvdir service, I expect two runsv instances to be 
running. One for Foo, one for bar. But on my system, only one instance 
for Foo is running, and bar/run is not being executed.

I have runit 2.1.2-29.

Has this feature been removed without updating the manpage?
I did not find anything in the archive.

Martin Castillo

To test this I used (also attached):
Foo/run:
#!/bin/bash
while :; do
	echo -n "FOO ";	date; sleep 3;
done

Foo/bar/run
#!/bin/bash
while :; do
	echo -n "BAR ";	date; sleep 3;
done

[-- Attachment #2: foo.tgz --]
[-- Type: application/x-compressed-tar, Size: 257 bytes --]

Re: runsvdir does not run runsv recursively, as is documented.

[Laurent Bercot]

>I'm trying to set up services, which are in subdirectories of other services. This is supported, according to the second paragraph of the runsvdir man page:
>
>runsvdir starts a runsv(8) process for each subdirectory,  or
>symlink  to a directory, in the services directory dir, up to
>a limit of  1000  subdirectories,
>
>In my directory service/ I have:
>Foo
>Foo/run
>Foo/bar
>Foo/bar/run

  That's not what the man page means. The "subdirectories" are
subdirectories *of dir*.
  runsvdir will understand service/Foo, and service/bar, but it will not
understand service/Foo/bar.

  The exception is if you have a service/Foo/log directory, but that's
handled by runsv, not runsvdir: service/Foo/log is a logger for
service/Foo.

--
  Laurent