This is probably something any SA should know... but I don't!
On CentOS 5 I can see what a process's current soft and hard limits are; /proc/<pid>/limits
However this isn't in the C4 kernel. Is there any easy way of determining what the process rlimit values are?
% uname -a ; cat /etc/redhat-release Linux c4 2.6.20.7 #3 Sun May 2 16:30:15 EDT 2010 i686 i686 i386 GNU/Linux CentOS release 4.8 (Final)
(yes, I know this machine should be updated, but...)
On Tue, Dec 06, 2011 at 01:08:32PM -0500, Stephen Harris wrote:
This is probably something any SA should know... but I don't!
...
% uname -a ; cat /etc/redhat-release Linux c4 2.6.20.7 #3 Sun May 2 16:30:15 EDT 2010 i686 i686 i386 GNU/Linux CentOS release 4.8 (Final)
(yes, I know this machine should be updated, but...)
That's not a CentOS-4 kernel... kernel-2.6.9-101.EL is the latest released
Tru
On Tue, Dec 06, 2011 at 07:25:26PM +0100, Tru Huynh wrote:
On Tue, Dec 06, 2011 at 01:08:32PM -0500, Stephen Harris wrote:
% uname -a ; cat /etc/redhat-release Linux c4 2.6.20.7 #3 Sun May 2 16:30:15 EDT 2010 i686 i686 i386 GNU/Linux CentOS release 4.8 (Final)
(yes, I know this machine should be updated, but...)
That's not a CentOS-4 kernel... kernel-2.6.9-101.EL is the latest released
OK, that was a usermode linux kernel. Here's a machine with 4.5 instead and 2.6.9-55.9.ELsmp
I can't upgrade these machines in a reasonable time period (production outage on core infra? Ugh) and need the values on the current systems.
(Huh, interesting, 4.6 with 2.6.9-89.0.9.EL does have /proc/<pid>/limits)
Dec 7, 2011 2:43 AM Stephen Harris lists@spuddy.org 작성:
I can't upgrade these machines in a reasonable time period (production outage on core infra? Ugh) and need the values on the current systems.
I also have few important systems that are stuck in Centos 4.x. Can't afford the downtime. So far it's fine. But as the end of life comes closer...... (fill in any admin rants here). :)