Sponsored Content
Operating Systems Linux Red Hat [help] how to send wall/broadcast message to all clients Post 302366648 by flekzout on Friday 30th of October 2009 04:00:13 AM
Old 10-30-2009
Quote:
Originally Posted by sahu.tapan
If you want send message to every user in your system no need to mentation the user.
You have to follow the below command. Message should be enclosed with double or single quote.

Code:
#wall "Message "

I want to send message to all clients/servers.. I have like more than 10 servers.. I want to send to all of them from one server.. instead I have to login through them one by one..
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How can I deny messaging which use "wall" to send message out?

Dear all, How can I deny messaging which use "wall" command to send message out? regards Wilson (7 Replies)
Discussion started by: wilsonchan1000
7 Replies

2. UNIX for Dummies Questions & Answers

send message across terminals

Hello: How would you send message to other unix users logged in into the system now.. what should i verify, before sending them a mail across that displays mesage on the terminal. Any man pages? Thanks, ST2000 (2 Replies)
Discussion started by: ST2000
2 Replies

3. UNIX for Advanced & Expert Users

Cron wall message problem

Operating system sun solaris 5.8 My problem is : crontab -e 15 16 * * * /bckscripts/oo vi /bcscripts/oo = wall " stop backup " the system at the 16:15 all day time doesn't display message " stop backup " What's the problem ??? i'am root user the follow is the root dir... (2 Replies)
Discussion started by: tt155
2 Replies

4. UNIX for Dummies Questions & Answers

Looking for an X11 Utility - Send Keystrokes to Multiple Clients

A long time ago, I frequently used a small X11 utility that allows you to manage multiple systems at the same time. It worked by opening a small window that had a button you used to "Add" X Clients to it. These would be xterms on different systems for example. You would then type inside that... (5 Replies)
Discussion started by: Alon.Albert
5 Replies

5. Programming

How to broadcast a message across the network using Socket programming in C??

My problem definition is ,I have to send a message from one node in a network and it has to be broadcasted to all other nodes in the network.The program what I have given below will be running in all the nodes in the network.The same program should be capable of sending(broadcasting) and receiving.... (1 Reply)
Discussion started by: vigneshinbox
1 Replies

6. Programming

How to broadcast a message ?

My problem definition is ,I have to send a message from one node in a network and it has to be broadcasted to all other nodes in the network.The program what I have given below will be running in all the nodes in the network.The same program should be capable of sending(broadcasting) and receiving.... (0 Replies)
Discussion started by: vigneshinbox
0 Replies

7. Shell Programming and Scripting

How to broadcast the message if any condition meets

Hi All, Can any1 help me out in broadcasting a message to all users if a condtion is meet. Like I am trying to get values from a directory for service monitoring. If a condition is meet it should broadcast the message. I try to use wall command but i m not sure how its works as its... (1 Reply)
Discussion started by: jojo123
1 Replies

8. Solaris

broadcast message from unix server

we enabled windows firewall and noticed that one unix sun server (solaris 9 ) are broadcasting on UDP port 14000 continous. We are running Oracle Application on this server, so I'm not sure if there is some service doing this, or any idea how to trace . Regards (1 Reply)
Discussion started by: maooah
1 Replies

9. Shell Programming and Scripting

Nc won't send udp broadcast!?

Greetings, I want to send broadcast udp from a script. This works but is not broadcast: echo -n "this is my message\r\n" | nc -u 192.168.0.12 5100 The broadcast version does not work: echo -n "this is my message\r\n" | nc -u 192.168.0.255 5100 Suggestions on the right way to do this... (2 Replies)
Discussion started by: anotherstevest
2 Replies
NSEND(1)							       nsend								  NSEND(1)

NAME
nsend - Send messages to users or groups SYNOPSIS
nsend [ -h ] [ -S server ] [ -U user name ] [ -P password | -n ] [ -C ] [ -a ] -i objectID | -c connNum[,...] | { [ -t recipient type ] -o recipient name | recipient name } message DESCRIPTION
With nsend, you can send messages to the user's workstations. nsend looks up the file $HOME/.nwclient to find a file server, a user name and possibly a password. See nwclient(5) for more information. Please note that the access permissions of .nwclient MUST be 0600, for security reasons. OPTIONS
recipient name recipient name is either the NetWare name of the user to receive the message or the name of an existing user group on that server. You can use wildcards in this specification. -o recipient name Specifies recipient's name. This can specify user or group. -t recipent type Specifies recipient's type. -c connNum[,...] Specifies connection numbers of recipients. You can use this option as workaround to deliver messages to directory services users. -i userID Specifies recipient's object ID. You can use this option as workaround to deliver messages to directory services users. message message is the message to be sent. Please note that this has to be a single command line argument. If you want to send a message that contains spaces, you have to quote them on the command line. For example, to annoy your system administrator, you should try nsend supervisor 'I know how this works!' Program first searches (wildcards allowed) bindery with recipients name and type. If user is found, message is sent to this user, if group is found, message is sent to this group. Other object types are ignored. If no suitable object was found in this phase, connection list for specified object is retrieved (no wildcards allowed) and message is sent to this object (including print servers and so on). No expansions on group is done this time. -a By default, nsend prepends 'From ....' text to message. You can suppress this by adding -a to command line. -S server server is the name of the server you want to use. -U user name If the user name your NetWare administrator gave to you differs from your unix user-id, you should use -U to tell the server about your NetWare user name. -P password You may want to give the password required by the server on the command line. You should be careful about using passwords in scripts. -n -n should be given if specified user does not have password. If neither -n nor -P are given, nsend prompts for a password. -C By default, passwords are converted to uppercase before they are sent to the server, because most servers require this. You can turn off this conversion by -C. BUGS
Directory services connection are not supported yet. Options -c, -i and -o cannot be used together. If user is specified multiple times (using wildcards in group specification or by repeating same number in -c), message is delivered multi- ple times to him. SEE ALSO
nwclient(5), nprint(1), slist(1), ncpmount(8), ncpumount(8) CREDITS
nsend was written by looking at mars_nwe's message handling. Thanks to Martin Stover <mstover@freeway.de>. Support for Netware groups by Philippe Andersson <philippe_andersson@ste.scitex.com>. Support for connections greater than 255 by Petr Vandrovec <vandrove@vc.cvut.cz>. nsend 04/07/1999 NSEND(1)
All times are GMT -4. The time now is 09:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy