Andrew Brown <atatat@atatdot.net> writes:

> off the top of my head, i'd say it's there to differentiate "cron,
> the running daemon who starts stuff" from "cron, a child of the
> aforementioned daemon who is now monitoring a job".

setproctitle()

> in the case of the syslog entry...i think it's just a side effect of
> the fact that openlog(3) is called with ProgramName as the ident.

Obviously.

/Johan