QNX6 & /etc/issue

In QNX4 when the login program was first executed, if there existed a
file called /etc/issue, then it’s contents would be displayed even
before the user tried to log in.

This file/feature does not seem to exist for QNX6. Is there a reason?
Or, is there a different way to do this in QNX6?

It is useful for things like:
Sorry, the system is being maintianed.
Logins are not allowed right now.


Bill Caroselli – Q-TPS Consulting
qtps@earthlink.net

Bill Caroselli <qtps@earthlink.net> wrote:

In QNX4 when the login program was first executed, if there existed a
file called /etc/issue, then it’s contents would be displayed even
before the user tried to log in.

This file/feature does not seem to exist for QNX6. Is there a reason?
Or, is there a different way to do this in QNX6?

It is useful for things like:
Sorry, the system is being maintianed.
Logins are not allowed right now.

it was discussed back in the QNX 6.1 days:
http://www.openqnx.com/PNphpBB2+viewtopic-t-236-.html

Frank Liu <fliu@mail.vipstage.com> wrote:
FL > Bill Caroselli <qtps@earthlink.net> wrote:

In QNX4 when the login program was first executed, if there existed a
file called /etc/issue, then it’s contents would be displayed even
before the user tried to log in.

This file/feature does not seem to exist for QNX6. Is there a reason?
Or, is there a different way to do this in QNX6?

It is useful for things like:
Sorry, the system is being maintianed.
Logins are not allowed right now.

FL > it was discussed back in the QNX 6.1 days:
FL > http://www.openqnx.com/PNphpBB2+viewtopic-t-236-.html

So, I guess that means no.

for tinit-initiated logins:

echo “this is a test” >/etc/issue
cat - >/usr/local/bin/startlogin
#!/bin/sh
/bin/cat /etc/issue
exec /bin/login
^D
chmod 711 /usr/local/bin/startlogin
sed s@/bin/login@/usr/local/bin/startlogin@ </etc/config/ttys >/tmp/tempfile
mv /tmp/tempfile /etc/config/ttys

You’ll need to restart tinit to make it work; tinit just reads
/etc/config/ttys once on startup. If you get it wrong, watch out: you won’t
be able to log in.

For getty, you should be able to customize your /etc/gettytab to relay short
messages via im=. I think our telnetd doesn’t perform the /etc/gettytab
lookup however so you may not have much luck trying to get the message out
directly with telnet. (someone correct me if I’m wrong)

“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:bja0ik$m3j$2@inn.qnx.com

Frank Liu <> fliu@mail.vipstage.com> > wrote:
FL > Bill Caroselli <> qtps@earthlink.net> > wrote:
In QNX4 when the login program was first executed, if there existed a
file called /etc/issue, then it’s contents would be displayed even
before the user tried to log in.

This file/feature does not seem to exist for QNX6. Is there a reason?
Or, is there a different way to do this in QNX6?

It is useful for things like:
Sorry, the system is being maintianed.
Logins are not allowed right now.


FL > it was discussed back in the QNX 6.1 days:
FL > > http://www.openqnx.com/PNphpBB2+viewtopic-t-236-.html

So, I guess that means no.

Thank you Eric. This works.

Why was that functionality removed from login?

Eric Johnson <eric@qnx.com> wrote:
EJ > for tinit-initiated logins:

EJ > echo “this is a test” >/etc/issue
EJ > cat - >/usr/local/bin/startlogin
EJ > #!/bin/sh
EJ > /bin/cat /etc/issue
EJ > exec /bin/login
EJ > ^D
EJ > chmod 711 /usr/local/bin/startlogin
EJ > sed s@/bin/login@/usr/local/bin/startlogin@ </etc/config/ttys >/tmp/tempfile
EJ > mv /tmp/tempfile /etc/config/ttys

EJ > You’ll need to restart tinit to make it work; tinit just reads
EJ > /etc/config/ttys once on startup. If you get it wrong, watch out: you won’t
EJ > be able to log in.

EJ > For getty, you should be able to customize your /etc/gettytab to relay short
EJ > messages via im=. I think our telnetd doesn’t perform the /etc/gettytab
EJ > lookup however so you may not have much luck trying to get the message out
EJ > directly with telnet. (someone correct me if I’m wrong)