UNIX for Advanced & Expert Users

Hi,

I have been trying to create a banner/login message (something for displaying the usage policy etc) to appear while I login using telnet/FTP to any Solaris (pref. Solaris9) machine. I have tried using /etc/issue and /etc/motd files. Both do not solve my need. In that, /etc/issue displays the whole message each time the login fails and the message in /etc/motd occurs only after logged into the session.

I need to display a message that occurs only once - i.e while opening a telnet session/FTP session. What should I do to get this running?

Regards,
M.

for telnet you could create a "/etc/default/telnetd" file

Code:

root@jumpy # cat /etc/default/telnetd
BANNER="\\n\\nThis should be a telnet banner\\n\\n"
root@jumpy # telnet localhost
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

This should be a telnet banner

login:

gP

just a doubt,

what if I have the same banner message in /etc/motd; /etc/issue and /etc/default/telnetd files

will the banner text of /etc/motd and /etc/issue files (displaying the banner for every failed and successful login ) do override that of /etc/default/telnetd

for ftp you could create the file in /etc/ftpd/banner.msg

Code:

root@jumpy # cat /etc/ftpd/banner.msg
test by pressy
root@jumpy # ftp localhost
Connected to localhost.
220-test by pressy
220-
220 jumpy FTP server ready.
Name (localhost:root):

you could change your banner file in /etc/ftpd/ftpaccess
"banner /etc/ftpd/banner.msg"

regards PRESSY

mhm.... just tried it. "/etc/default/telnetd" is displayed first, then /etc/issue.... /etc/motd is only displayed after a successful login, but it does not override it..


gP

I have created this telnetd file (it did not exist previously) and have entered the neccessary details. It still does not work.
By the way, there exists another server where the messages appear as required without the existance of both these files (/etc/default/telnetd and /etc/ftpd/banner.msg). How is that?

Thanks.

if the working box is using the same os as the non-working box --- investigate how it works on that good box and copy the change into the other box ... cuts down on the guesswork ...