On Mon, 4 Aug 2014, Philip Guenther wrote:
On Sat, Aug 2, 2014 at 7:06 AM, Ed Hynan eh_l...@optonline.net wrote:
Saturday morning, saw this in /var/log/messages:
Aug 2 08:29:12 lucy su: default: setting resource limit openfiles:
Invalid argument
(BTW, I quoted a line I produced by hand:
On Tue, Aug 5, 2014 at 6:49 AM, Ed Hynan eh_l...@optonline.net wrote:
On Mon, 4 Aug 2014, Philip Guenther wrote:
On Sat, Aug 2, 2014 at 7:06 AM, Ed Hynan eh_l...@optonline.net wrote:
...
That indicates that the requested -cur value was greater than the requested
-max value, if any, or
On Tue, 5 Aug 2014, Philip Guenther wrote:
On Tue, Aug 5, 2014 at 6:49 AM, Ed Hynan eh_l...@optonline.net wrote:
Failure to set the resource limits isn't considered fatal for
setusercontext(). It would be Bad if a typo there could leave you unable
to login or su to root...
Agreed. My case
On Sat, Aug 2, 2014 at 7:06 AM, Ed Hynan eh_l...@optonline.net wrote:
Saturday morning, saw this in /var/log/messages:
Aug 2 08:29:12 lucy su: default: setting resource limit openfiles:
Invalid argument
That indicates that the requested -cur value was greater than the requested
-max value,
Saturday morning, saw this in /var/log/messages:
Aug 2 08:29:12 lucy su: default: setting resource limit openfiles: Invalid
argument
That's from /etc/weekly, which uses 'su -m nobody' for locate db update
on line 52. The log message can be produced by hand with, e.g.:
# echo /bin/echo FOO |
5 matches
Mail list logo
