David Boyes wrote:
Given that I seem to have that right and seem to be at a current-enough (too current?)
level of SLES 8, what else do I look for?
I'm kind of puzzled what you're asking. Is it not working, or is it
doing something weird?
I'll go with, It's doing something weird.
At the end of
Sent: Tuesday, April 27, 2004 8:56 AM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] Monthly forehead bruising: inittab
ctrlaltdel
David Boyes wrote:
Given that I seem to have that right and seem to be at a
current-enough (too current?) level of SLES 8, what else do I
look for?
I'm
Nick Laflamme wrote:
So, my next puzzle is, what's with the unknown runlevel? Or, just how
screwed up is this particular Linux image? Fortunately, it's my test
image. I haven't rebuilt it in a few weeks; must be time to do so. :-)
The 'runlevel' command should tell you...
I am not sure whether
AM
To: [EMAIL PROTECTED]
Subject: Re: Monthly forehead bruising: inittab ctrlaltdel
Nick wrote:
I know I've asked about this before on this list, and several of you
have repeated the syntax for /etc/inittab, typically:
ca:12345:ctrlaltdel:/sbin/shutdown -h now
Just looked at mine and it's
Should doesn't count. How many times have we heard, In theory,
practice and theory agree. In reality, theory and practice differ?
This is one of those times. :-)
Rob van der Heij's warning bout YaST2-sshinstall was probably exactly on
target: when I reran the install process today for my test
Laflamme
Sent: Tuesday, April 27, 2004 2:53 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] Monthly forehead bruising: inittab
ctrlaltdel
Should doesn't count. How many times have we heard, In theory,
practice and theory agree. In reality, theory and practice differ?
This is one of those
Hall, Ken (IDS ECCS) wrote:
On the original system, was there a line in inittab similar to the following?
# The default runlevel is defined here
id:3:initdefault:
Yes, that was there. I still ended up in runlevel unknown.
With no default runlevel, I'm surprised anything was working.
In retrospect,
I'm back for my monthly efforts to get SIGNAL SHUTDOWN support in a
SLES8 image working under VM. In the month since I last beat my head
against this particular wall, I've made sure this image has the latest
and greatest patches on it. It's at SP 3 and some other fixes released
by SuSE,
Your responses are correct and inittab looks OK (from memory)...
Is it not working? The first time you will need to restart the init
process. I don't recall the exact syntax, but it should be in the
archive.
On Mon, 2004-04-26 at 15:32, Nick Laflamme wrote:
I'm back for my monthly efforts to
Is there any sort of verification tool for /etc/inittab to
rule out any
manner of stupid typos, bad assumptions, and other faults?
IEHIBAL is pretty much it. You can compare it against the docs in 'man 5
inittab', but it's pretty much your gun, your foot.
What kinds of log messages does one
telinit q
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rich
Smrcina
Sent: Monday, April 26, 2004 4:52 PM
To: [EMAIL PROTECTED]
Subject: Re: Monthly forehead bruising: inittab ctrlaltdel
Your responses are correct and inittab looks OK
I have an exec that issues the shutdown command and waits for a CP
message. It works for me.
I have the VM operator issue it prior to a VM roll and it seems to work
ok. you should be getting a CP message HCPSIG2113I or HCPSIG2112I.
I can send this EXEC if you like
Nick Laflamme wrote:
I'm
You can certainly issue individual SIGNAL SHUTDOWNs (manually or via an
EXEC like yours), but VMs SHUTDOWN command can wait a designated amount
of time (which is tailorable) to allow the Linux machines to shut down
via the signal.
On Mon, 2004-04-26 at 16:30, Scorch Burnet wrote:
I have an exec
: Re: [LINUX-390] Monthly forehead bruising: inittab ctrlaltdel
Your responses are correct and inittab looks OK (from memory)...
Is it not working? The first time you will need to restart the init
process. I don't recall the exact syntax, but it should be in the
archive.
On Mon, 2004-04-26
forehead bruising: inittab ctrlaltdel
Your responses are correct and inittab looks OK (from memory)...
Is it not working? The first time you will need to restart the init
process. I don't recall the exact syntax, but it should be in the
archive.
On Mon, 2004-04-26 at 15:32, Nick Laflamme wrote
: Monday, April 26, 2004 5:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Monthly forehead bruising: inittab ctrlaltdel
Do you also need in the /etc/zipl.conf kernel parameter line vmpoff=LOGOFF
vmhalt=LOGOFF or do I just have that for historical reasons?
What level of VM? Does CP Q SIGNALS show your
at that point, then you can take
those parms out.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Marcy Cortes
Sent: Monday, April 26, 2004 5:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Monthly forehead bruising: inittab ctrlaltdel
Do you
Nick wrote:
I know I've asked about this before on this list, and several of you
have repeated the syntax for /etc/inittab, typically:
ca:12345:ctrlaltdel:/sbin/shutdown -h now
Just looked at mine and it's
ca::ctrlaltdel:/sbin/shutdown -h now
Perhaps you are not in run levels 1
18 matches
Mail list logo
