måndag den 26 september 2011 klockan 16:24 skrev Christian Kastner detta:
> >
> > The file 'limits.conf' consists of commented out text and empty lines,
> > no active content.
>
> Did you also check /etc/security/limits.d/ ?
Empty, not even any black matter!
>
> > The 'cron' description is the original
> ...
> > # Sets up user limits, please define limits for cron tasks
> > # through /etc/security/limits.conf
> > session required pam_limits.so
>
> This line means that cron will use whatever limits are configured on
> your system in general -- we don't ship any limits with cron.
>
> So the error you are seeing must come from either limits.conf or
> limits.d, at least that is my understanding of pam_limits(8).
My best guess at the moment is that the alteration of pam_1.1.2-3 to
027_pam_limits_better_...
which began reading "/proc/1/limits". However, cron runs underprivileged,
hence the process might not able to read that file for getting the value
of "Maximum realtime priority". (Guessing somewhat arbitrarily). My original
problem stems from May, which fits with pam_1.1.2-3.
Best regards,
Mats E A
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
