Our hardware people moved all the penguins to new DASD last night, so we took
then all down, along with the two zVMs. When the copying was done, both zVMs
came back up without problem, along with all the penguins... Except one.
The one zLinux image comes up, but gets the following messages
Perhaps it is just the geek in me, but I think this is cool:
SP1 adds mainframe capitalization with CPU hotplug support for IBM
S/390
and zSeries machines, enabling a physical CPU to be exchanged during
runtime and keeping the system up and running even through server
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Jon Brock
Sent: Wednesday, July 13, 2005 8:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES Service Pack Released
Perhaps it is just the geek in me, but I think this is cool:
SP1 adds
IPL from the reader using the installation kernel and initrd. Insmod
the DASD driver and mount your file systems. Get the network up. Copy
the kernel RPM from one of the other systems to the failed one. Chroot
to your root file system. Install the RPM. Run zipl. Do a depmod -a
Is there any way to limit what processes someone could kill when using
Sudo?
Our websphere administrator wants the authority to kill a hung java thread
should the need arise, and he wants the root password. I do not want to and
will not give it to him. I am being directed by my management to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Melin wrote:
| Is there any way to limit what processes someone could kill when using
| Sudo?
|
| Our websphere administrator wants the authority to kill a hung java thread
| should the need arise, and he wants the root password. I do not want
I was wondering about that. Time to find new proofreaders.
Hannes Reinecke wrote:
(Either the webserver is seriously out-of-date or someone did not read
it properly, but this really should read 'SP2 released'. Anyhow.)
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
create a script to kill the specific process (where the script checks, if
the process to kill belongs to websphere) and define a sudo configuration
to regulate access to this script.
Regards,
Juergen Friedrichs
PGP Fingerprint: 15B9 DF14 12EA 96C7
-Original Message-
From: James Melin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 13, 2005 02:02 PM
To: LINUX-390@VM.MARIST.EDU
Subject: SUDO access granularity
Is there any way to limit what processes someone could kill when using
Sudo?
Our websphere administrator wants the
In a HA cluster, I want to 'rexec' to z/VM to kill the faulty node. But
stonith does not seem to have any devices for this. I looked at all the
stonith devices. None of them seems to be suitable in z/VM environment.
The HA redbook talks about 'rexec'ing to z/vm to shutdown the faulty node.
We use REXEC to VM. Yes it is available.
Ranga Nathan wrote:
In a HA cluster, I want to 'rexec' to z/VM to kill the faulty node. But
stonith does not seem to have any devices for this. I looked at all the
stonith devices. None of them seems to be suitable in z/VM environment.
The HA redbook
I have run into a problem running PHP code using preg_match_all.
I'm racking my brain trying to figure out a solution. Maybe someone
else knows the answer?
I have two boxes that I'm working on, and I've moved some PHP code from
one box using PHP version 4.2.2 (Intel running Red Hat) to another
12 matches
Mail list logo
