I did a bit of cleanup on klogd in pending and can probably promote it
now (maybe -s should auto-fallback if it can't open /proc/kmsg), but...
I don't really use this command in my systems, and I have no tests.
Does anybody have a good set of tests (maybe to run in a mkroot image)
to confirm that klogd is Doing The Thing?
I have a similar issue with crond/crontab. I conceptually understand
what crond does, although A) I almost exclusively use the "at" command
when it's available, B) 700 lines seems kind of overkill here, C) I keep
thinking daemons in general should have more shared infrastructure than
they do (WHY is this _conditionally_ calling syslog() itself, what the
HECK does it think it's doing with those days[] and months[] arrays, it
has a sendmail() function?)
But I never understood "crontab". (Nor why posix has crontab but not
crond.) We don't have "sshtab", we have ~/.ssh/files that the daemon
parses as necessary. Why the heck would crond be any different?
Rob
P.S. My devuan install hasn't got a "crond" man page but DOES have
/etc/crontab, /etc/cron.d, /etc/cron.daily, /etc/cron.hourly,
/etc/cron.monthly, /etc/cron.weekly, and /etc/cron.yearly. All in the
top level of /etc. I am NOT DOING THAT for toybox...
_______________________________________________
Toybox mailing list
Toybox@lists.landley.net
http://lists.landley.net/listinfo.cgi/toybox-landley.net
