Yes HOD was used with HPUX and will be used with linux on z.
Now they tell me they had on HPUX and stiil have on z a problem with processes
left by users not terminating out of HOD properly. Processes that are left
apparently use quite a bit of cpu. They reworked a kill script they ran on HPUX
Hi there.
We have autogenerated mac addresses for our zLinux servers (ip-only traffic)
I have tested and verified that the mac-address for the network adapter changes
between z/VM logoff-logon ( shutdown + start ).
Well, that's no surprise, that's what we wanted :-)
BUT:
The license for for a
You can hard-code the MAC address into /etc/sysconfig/network/ifcfg-eth0
(SLES 11 SP1):
# cat ifcfg-eth0
...
STARTMODE='auto'
USERCONTROL='no'
LLADDR='02:12:34:56:78:90'
UNIQUE=''
NAME='OSA Express Network card (0.0.0800)'
Regards,
-
Thang Pham
IBM Poughkeepsie
On Friday, 11/18/2011 at 11:44 EST, Agblad Tore tore.agb...@volvo.com
wrote:
Hi there.
We have autogenerated mac addresses for our zLinux servers (ip-only
traffic)
I have tested and verified that the mac-address for the network adapter
changes
between z/VM logoff-logon ( shutdown + start ).
Run-away processes from lost terminal (or lost session, lost
pseudo-terminal) is a common problem. Yes, I've heard of it before.
(Was/is not specific to HOD.)
Theoretically, a process gets a HUP signal (hangup) when the session
is dropped. For the signal to work, the whole TTY/PTY/PTS chain
On 11/18/2011 at 12:33 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
I recommend against coding LLADDR in your Linux config.
The problem isn't the system administrators doing it, but the tools they use.
I'm hopeful that will get fixed for at least SLES11 SP2.
Mark Post
On 11/18/2011 at 12:00 PM, Thang Pham thang.p...@us.ibm.com wrote:
You can hard-code the MAC address into /etc/sysconfig/network/ifcfg-eth0
You can, but that can cause serious problems at the z/VM level. There have
been cases where a hard coded MAC address in a Linux guest has caused another
