If cron accepts the -f option, you can make it persistent.
Even if not (ie. with older releases), you could too, using the -d option
and discarding the debug output to /dev/null, but this is more a kludge than
a solution.
Both options keep cron in the forground, this is needed for $ZZKRN to be
able to track it.
> Anyhow, the way you can make OSS processes
> persistent is not very amazing.
Why? I think it works quite well and I'm using it since a long time now, for
cron, inetd, named and even for samba.
Bye, Jojo