** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527723
Title:
atd doesn't increase limit load factor on smp systems (upstart)
To manage notifications about this bug go to:
** Bug watch added: Debian Bug tracker #79372
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79372
** Also affects: at (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79372
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
** Changed in: at (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527723
Title:
atd doesn't increase limit load factor on smp systems (upstart)
--
ubuntu-bugs
atd process pid:
/var/run/atd has the right pid of the atd process.
So I doesn't understand the point that upstart follows the awk pid.
--
atd doesn't increase limit load factor on smp systems (upstart)
https://bugs.launchpad.net/bugs/527723
You received this bug notification because you are a
Another general solution could be the reinventing auf /etc/defaults for
tweaking service confgurations.
e.g. cron loglevel coud be tweaked this way before the migration to upstart.
--
atd doesn't increase limit load factor on smp systems (upstart)
https://bugs.launchpad.net/bugs/527723
You
The atd initscript at the point this was converted to Upstart *DID NOT*
have this code, that makes this a wishlist only.
Unfortunately your patch is incorrect; Upstart will folllow the awk
process pid, rather than atd's. Also this kind of grep/awk on every
boot for everyone is exactly the kind
Changing the upstart job to the following will fix the issue
exec atd -l $(awk '/^processor/{cpu++}END{load=cpu-0.4; if (cpu 2) load=1.5;
print load;}' /proc/cpuinfo)
** Attachment added: at.patch
http://launchpadlibrarian.net/39762315/at.patch
--
atd doesn't increase limit load factor on
