Issue chkconfig boot.sysctl on or consider using /etc/init.d/boot.local instead.
Regards, Kevin -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wiggins, Mark Sent: Tuesday, May 23, 2006 8:41 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Question about sysctl.conf Ya, unfortunately I guess, that's what I've got. boot.sysctl No B -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Dell Harris Sent: Tuesday, May 23, 2006 11:22 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Question about sysctl.conf Bring up YaST2 -> System -> Runlevel Editor....Click on expert mode. Scroll down to boot.sysctl and ensure that the 'B' box is checked. >>> "Meanor, Tim" <[EMAIL PROTECTED]> 05/23/06 9:13 AM >>> What makes you think sysctl.conf isn't being read at boot time? It should be. I don't have a SLES system in front of me, but on Red Hat, the /etc/rc.sysinit script applies the settings in sysctl.conf to the running kernel. SLES probably has a similar init script. ----- Original Message----- From: Linux on 390 Port [mailto:LINUX- [EMAIL PROTECTED] On Behalf Of Wiggins, Mark Sent: Tuesday, May 23, 2006 11:00 AM To: LINUX- [EMAIL PROTECTED] Subject: Question about sysctl.conf So, way back when we made a decision to turn on the timer patch for all of our SuSE SLES9 images running on z/VM 5.1. Recently, I noticed (after all this time) that the /etc/sysctl.conf file does not get read at boot time and therefore, we've been running with the timer patch off. This now generates a few questions... 1) If the timer patch has been off for all of this time, is it worth turning on now? We haven't had any significant performance issues to date so how much difference would it really make now? In looking at the average CPU for 2 test images (1 with the patch on, 1 with it off) over the course of a day or so, the one with the "timer patch on" ran at an average of 0.17% CPU while doing nothing, and the one with the "timer patch off" ran at an average of 0.19% CPU. I could see this possibly mattering with hundreds of images, but we're somewhere between 30- 40. 2) If we decide to turn the patch on, how do you get it to stay on across an IPL. I've included "kernel.hz_timer=0" in the sysctl.conf, but it doesn't appear to be read after boot. What are other people doing with this? 3) Are there any particular instances where you wouldn't turn the patch on? E.g. a time server or maybe a mail server??? I don't know... Only test servers??? Etc... Mark Wiggins University of Connecticut Operating Systems Programmer 860- 486- 2792 ---------------------------------------------------------------------- For LINUX- 390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX- 390 or visit http://www.marist.edu/htbin/wlvindex?LINUX- 390 ---------------------------------------------------------------------- For LINUX- 390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX- 390 or visit http://www.marist.edu/htbin/wlvindex?LINUX- 390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390