Re: /etc/issue

Wayne Betts <wbetts@xxxxxxx> · Mon, 30 Jan 2006 17:14:10 -0500

Coleman, Kelley (HAC) wrote:
I log in using ssh on Reflection, which apparently is controlled by the
sshd_config file.  My BANNER parameter shows up there no problem, thanks
to other guidance I received here.
The place I'm trying to get the banner is on the console (which I rarely

use), at the login page.  I was pointed to the /etc/issue file.  I put

the banner verbiage in there, but it doesn't show up on the console. I'm

almost wondering if there isn't a bitmap I can create then make that the

background.  I don't know...I'm starting to give up.

Updating /etc/issue should be effective immediately...  but each console 
has to have a reason to notice the change. 
A reboot would certainly do it, but isn't necessary. 
Quick lesson:

Each console is a running process (mingetty), typically configured to 
respawn (in /etc/inittab) if it ever exits. 
So, how can you make it exit?

One way that requires the least Linux knowledge is to simply login to 
each console and log back out.

Then the updated /etc/issue should appear.  Repeat for each console.  
(Ctrl-Alt-F[123456]  (though only Alt-Fx is needed when switching between

text consoles, but how many parenthesis deep should I go in this 
explanation?  :-))
Alternatively, you could probably kill each mingetty using your favorite 
method, eg.  "ps -(your favorite options) |grep mingetty" followed by

"kill {fill in the pids}".  Or use "killall mingetty".  Lots of other 
ways possible too.  Experiment.  Sue for your money back if this advice 
doesn't work or causes problems... :-)
- Wayne (still not "Wayner")

-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Michael Velez
Sent: Monday, January 30, 2006 1:50 PM
To: 'General Red Hat Linux discussion list'
Subject: RE: /etc/issue

-----Original Message-----

From: redhat-list-bounces@xxxxxxxxxx

[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Coleman, Kelley 
(HAC)

Sent: Monday, January 30, 2006 3:21 PM

To: General Red Hat Linux discussion list

Subject: /etc/issue
Is there a way to have changes made to the /etc/issue file active 
without rebooting the server?  I've added a smattering of text per ISO

request that I need to prove works, but can't reboot the system for 
several days.  It doesn't seem to just show up, so I figure a restart 
of some service might make it happen.  Any thoughts?
Kelley Coleman
Database Administrator
VA Health Administration Center
Denver, Colorado
303-331-7521-o

Updating /etc/issue should not require a reboot (I've tested this on my
RHEL4 and it still works).
This may be a silly question but have you tried just hitting return to
get a new login prompt message?
Michael
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

Re: /etc/issue

Relevant Pages