Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 15
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 ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,778

    About wall command


    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

  2. #2
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,677
    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?

    Regards
    Robert

    Linux
    The adventure of a life time.

    Linux User #296285
    Get Counted

  3. #3
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,778
    Quote Originally Posted by Lazydog View Post
    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

  4. #4
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,677
    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

    Regards
    Robert

    Linux
    The adventure of a life time.

    Linux User #296285
    Get Counted

  5. #5
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,778
    Quote Originally Posted by Lazydog View Post
    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

  6. #6
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,677
    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.

    Regards
    Robert

    Linux
    The adventure of a life time.

    Linux User #296285
    Get Counted

  7. #7
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,778
    Quote Originally Posted by Lazydog View Post
    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

  8. #8
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,677
    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.

    Regards
    Robert

    Linux
    The adventure of a life time.

    Linux User #296285
    Get Counted

  9. #9
    Linux Guru
    Join Date
    Sep 2004
    Posts
    1,778
    Quote Originally Posted by Lazydog View Post
    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?

  10. #10
    Linux Enthusiast
    Join Date
    Aug 2006
    Location
    Portsmouth, UK
    Posts
    539
    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
    RHCE #100-015-395
    Please don't PM me with questions as no reply may offend, that's what the forums are for.

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •