sor...@cydem.org wrote:
Jamie ja...@geniegate.com writes:
Dag-Erling Smørgrav d...@des.no writes:
How about disabling atrun?
I use at/batch *constantly* (especially batch)
Wow. I don't know of anybody else who does... I always thought of it
as a relic.
I use at
Jamie ja...@geniegate.com writes:
Dag-Erling Smørgrav d...@des.no writes:
How about disabling atrun?
I use at/batch *constantly* (especially batch)
Wow. I don't know of anybody else who does... I always thought of it
as a relic.
DES
--
Dag-Erling Smørgrav - d...@des.no
I'm running cron in a jail, and I see these errors filling up crons
logfile
It *appears* to be coming from atrun, wanting to set up priority
from /etc/login.conf
if (setusercontext(NULL, pentry, uid, LOGIN_SETALL
~(LOGIN_SETPRIORITY | LOGIN_SETPATH | LOGIN_SETENV)) !=
Jamie ja...@geniegate.com writes:
I actually very much do NOT want atrun to be tinkering with the
priority (as I'd like to have it run in the idle task eventually)
Is there a way, short of recompiling, that I can convince atrun
not to do this?
How about disabling atrun?
DES
--
Dag-Erling
