On Wed, 3 Dec 2003 21:59:23 -0600 Adam Thornton said:
I suggest that everyone interested in this discussion read ESR's new
_The Art of Unix Programming_, and not just because I got him to change
something on page 4 that will bring great glee to the members of this
list. In fact, the very problem
On Wednesday, 12/03/2003 at 07:20 CST, Adam Thornton
[EMAIL PROTECTED] wrote:
On Wed, 2003-12-03 at 18:54, Romney White wrote:
Mark:
VSWITCH has an *optional* associated OSA Express device. If you don't
have one, you don't have external connectivity, but a VSWITCH is just
really a QDIO
Maybe I've been working under a misperception. I always thought that the
k_timer patch from SLES 7 was incorporated into SLES 8. If I am reading
the listserv correctly, the patch is in SLES8 but not turned on? I've
searched the web for any information I can about this and have turned up
nil. I
The December brochure may be found at
http://www.vm.ibm.com/events/hill1218.pdf. Register by posting to the
HILLGANG list.
In the SLES7 2.4.7 kernel, the timer patch added an option called (IIRC) hz_timer
to the kernel that could be enabled at kernel build time. SuSE supplied two different
kernels, one with the
feature enabled, the other disabled.
The patch was enhanced somewhere between 2.4.7 and 2.4.19 (SLES8)
note that there are some issues with this befor sles8 service pack 3. with
it enabled, it can lock your guest during very long i/o's.
I've heard of it happening with the creation of large tars. with us, it was
running verifies against a 70gig database.
-Original Message-
From: Hall,
But whose crack? In Australasia that word is often used for the fissure
between the right and left backside cheeks.
I forbear to comment further.
On Thu, 04 Dec 2003 02:46, you wrote:
Nice collection showing that SCO/Caldera people were involved with
RCU/JFS/etc. development.
With some SLES 7 update the k_timer kernel became available that had the
on-demand timer. At that time it was a configurable option at kernel
build time. Because you lose support with building your kernel, and
since keeping two different kernels is a pain this has become the
hz_timer /proc
This was reported to us, but never confirmed. We had been getting some I/O hangs that
IBM suspected were related to this, but we were never able to catch it in the act.
When we DID see hangs, as
often as not hz_timer was disabled because the sysctl interface didn't work at boot
time.
On Thu, Dec 04, 2003 at 08:31:48AM -0500, A. Harry Williams wrote:
On Wed, 3 Dec 2003 21:59:23 -0600 Adam Thornton said:
I suggest that everyone interested in this discussion read ESR's new
_The Art of Unix Programming_, and not just because I got him to change
something on page 4 that will
Greetings; (Posted to VMESA-L and VSE-L and LINUX-390)
- - Now in its sixth year! - - Includes VSE and linux/390!
I have set up a public service web page at
http://www.eskimo.com/~wix/vm/
for posting positions available and wanted for VM, VSE and linux/390.
Please visit the web
From what I've seen of recent RedHat systems, they are using an initrd,
so there *is no* DASD= token in the parm line as the system is IPLed.
There are variations on this theme, but one is
IPL with RAMDISK (initrd)
run module-loading logic from the RAMDISK
mount the
(using /proc-ish technology for various interfaces)
It strikes me that this would be an interesting experiment; the strength
of Linux is that, with the source code, any individual can try out these
kinds of ideas.
I will grant, though, that the someone performing the experiment may find
Another way to turn off the timer is:
echo 0 /proc/sys/kernel/hz_timer
in boot.local.
On Thu, 2003-12-04 at 10:31, Kevin Ellsperman wrote:
Maybe I've been working under a misperception. I always thought that the
k_timer patch from SLES 7 was incorporated into SLES 8. If I am reading
the
Has anyone seen this kind of oddness before:
A look at the process table does not show the processes listening and owned by
init, things like root sshd or portmap:
[EMAIL PROTECTED] root]# ps -aef
UIDPID PPID C STIME TTY TIME CMD
root 1 0 0 09:52 ?
Has anyone tried the vmpoff or vmhalt parameters in
/etc/zipl.conf for rhel3?
I seem to be able to get mem= and cio_ignore= to work
by coding them /etc/zipl.conf, but the system does not
seem to respond correctly to vmpoff=LOGOFF or
vmhalt='I CMS'.
=
Jim Sibley
Implementor of Linux on
On Iau, 2003-12-04 at 18:04, Wilson, Eric wrote:
Has anyone seen this kind of oddness before:
A look at the process table does not show the processes listening and owned by
init, things like root sshd or portmap:
I've seen a bug report about this somewhere with seekdir on /proc
causing a
Alan;
It appears top does behave the same way:
15:57:16 up 6:05, 3 users, load average: 0.04, 0.02, 0.00
32 processes: 30 sleeping, 2 running, 0 zombie, 0 stopped
CPU states: cpuusernice systemirq softirq iowaitidle
total0.0%0.0%0.1% 0.0%
Mike,
Ian McKay from Amdahl provided me with the following information,
which has cleared up the final issue, i.e. No problems under MVS with BFP
instructions.
Amdahl 0700 (and 1000 , and 0800 , and 2000A) processors do NOT have Binary
Floating Point (BFP) otherwise referred to as IEEE as
I need to be able to set the ulimit for nofile - the maximum number of open
files. It defaults to 1024 and WebSphere V5 needs this value set
significantly higher. I can change this value from the command line as
root, I cannot set this value in /etc/security/limits.conf. Anything I
specify in
for system wide changes, try putting
sysctl -w fs.file-max=nn
in /etc/init.d/boot.local for SuSE or
/etc/rc.d/rc.local for RHEL3.
=
Jim Sibley
Implementor of Linux on zSeries in the beautiful Silicon Valley
Computer are useless.They can only give answers. Pablo Picasso
Rather than use rc.local, RH provides /etc/sysctl.conf
Cheers;
E!
-Original Message-
From: Jim Sibley [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2003 5:55 PM
To: [EMAIL PROTECTED]
Subject: Re: ulimit settings
for system wide changes, try putting
sysctl -w
This url was posted in the grc.techtalk
newsgroup and looked very interesting - enjoy all.
http://www-106.ibm.com/developerworks/linux/library/l-roadmap.html
IBM
e-business architect Chris Walden is your guide through a nine-part developerWorks
series on moving your operational skills from a
While trying to compile glibc 2.3.2 using gcc 3.3, I get the following
error:
s390-slackware-linux-gcc
../sysdeps/unix/sysv/linux/ustat.c -c -std=gnu99 -O2 -Wall -Winline -Wstrict
-prototypes -Wwrite-strings -g -I../include -I. -I/tmp/build-glibc-2.3.
24 matches
Mail list logo
