RE: 1000-directory limit for svscan

Andrew Catton wrote:
> Does anyone know the reason for this hardcoded limit in svscan?  =20
> We're working with a fairly unusual deployment approach which =20
> requires us to exceed it.  I've increased the SERVICES size, but =20
> would like to know if I'm walking into some trouble that the limit =20
> was meant to prevent..

Just for the record, I have been running into this as well.  I use =
svscan at
client sites to control large numbers of services across clusters of
machines.  As machines are getting bigger, we want to run more than 1000
service instances per machine.

Splitting things into /service{1..n} isn't really nice, because then =
things
get special names.

Regards,

Jan Mikkelsen