About wall command

[satimis]

Hi folks,


About "wall", the broadcasting command, notifying the users of important notice by Adminstration. Only the login users can receive the broadcasting message. If a message, e.g. notifying the users of the shutdown of the server for repair after half an hour and advising them saving their work, those users who login after broadcasting may NOT be aware of the message. Any suggestion? TIA


B.R.
satimis

[Lazydog]

I take it your user will be logging in via telnet/ssh?

If so why not use the issue and issue.net files to inform them of the date and time the systems will be going down?

[satimis]

I take it your user will be logging in via telnet/ssh?

Thanks for your advice.

login via ssh

If so why not use the issue and issue.net files to inform them of the date and time the systems will be going down?

I have the said file on /etc/issue.net

It is a text file. "man issue" doesn't provide much info re how to use it. Whether login as super user to edit this file putting the msg there? If YES, then each time the msg has to be deleted afterwards.

TIA

satimis

[Lazydog]

It is a simple text file that is displayed when logging in.

ISSUE is used when you log in local

ISSUE.NET is used when you log in remotely

[satimis]

It is a simple text file that is displayed when logging in.

ISSUE is used when you log in local

ISSUE.NET is used when you log in remotely

Will the message added on the file be automatically removed on rebooting the server? Or it has to be removed manually? TIA

B.R.
satimis

[Lazydog]

Manually. I would create a script that would replace the file once the server is rebooted. That way after the server is rebooted your normal greatings will be shown again.

[satimis]

Manually. I would create a script that would replace the file once the server is rebooted. That way after the server is rebooted your normal greatings will be shown again.

Noted and thanks.


How about those users already login. Shall I run "wall" and "issue" simultaneously?


B.R.
satimis

[Lazydog]

Yeah. ISSUE would only be displayed to new users logging in and wall would tell everyone that is logged in before you changed the issue file.

1. edit issue file and change to what you need them to know.
2. issue the wall command.
3. setup a batch file to replace the issue file once the server is rebooted.
(this could be a script that alway runs at boot to ensure the correct issue file is in place)
4. reboot when you taold everyone that it was going to be rebooted.

I would make it very obvious that thwe system is going to be rebooted in the issue file as some people tend to skip right by this. All Caps and/or special chars to grab their attention.

[satimis]

Yeah. ISSUE would only be displayed to new users logging in and wall would tell everyone that is logged in before you changed the issue file.

1. edit issue file and change to what you need them to know.
2. issue the wall command.
3. setup a batch file to replace the issue file once the server is rebooted.
(this could be a script that alway runs at boot to ensure the correct issue file is in place)
4. reboot when you taold everyone that it was going to be rebooted.

I would make it very obvious that thwe system is going to be rebooted in the issue file as some people tend to skip right by this. All Caps and/or special chars to grab their attention.

Thanks for your advice.

Another thought, would it be easier sending all users an urgent mail informing them server will be shutdown after half an hour?

[matonb]

Another thought, would it be easier sending all users an urgent mail informing them server will be shutdown after half an hour?

Sending an email to all users concerned is a good idea