To answer myself to prevent someone else from doing that: no, it's
really not enough. When you issue at command it should be checked then
as well. Which means that best would be to have something usable at both
times (init process, issuing at commands). But is it still aok to script
it or is that
Would modifying /etc/init.d/atd be good enough solution? Check if the
spool directories are empty and if they are then do not start the
daemon? Or is a more heavy duty solution desired?
This really doesn't sound to me like it should be very complex fix to
catch most of the situations where it can
** Changed in: at (Ubuntu)
Assignee: Scott James Remnant = (unassigned)
--
Only start atd when needed?
https://bugs.launchpad.net/bugs/12253
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Changed in: at (Ubuntu)
Status: Unconfirmed = Confirmed
--
Only start atd when needed?
https://launchpad.net/bugs/12253
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: at (Ubuntu)
Assignee: (unassigned) = Scott James Remnant
--
Only start atd when needed?
https://launchpad.net/bugs/12253
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
