Sponsored Content
Top Forums UNIX for Advanced & Expert Users To send a message to another system Post 302120536 by sumitpandya on Thursday 7th of June 2007 01:30:40 AM
Old 06-07-2007
Client Server Communication

You definately require to run some TCP/IP server on those system. You need not write any such server. You can use a marvolus tool named "NetCat (nc)". You can create a Shell Script and invoke that from "inet".
Other approach could be invoke such script from "r" (rsh, rexec) utilities, that may open some security threats.
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

Sendmail keep a user from send message

Hello, i have a problem with my sendmail, i want' to keep a user from sending mail, how can i process ? My user is titi, and i don't want' that titi can't send mail via sendmail is it possible ? thnak a lot (1 Reply)
Discussion started by: westside
1 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. Shell Programming and Scripting

How to Send warning message to user

Hai..I have one question in unix Shell script.Following is the script System Configuration: lcpu=4 mem=8192MB kthr memory page faults cpu ----- ----------- ------------------------ ------------ ----------- r b avm fre re pi po fr sr cy ... (1 Reply)
Discussion started by: sollin
1 Replies

4. UNIX for Dummies Questions & Answers

Send message from Unix to PC

What is the best way to send message from Unix script to PC users connected to the box ? I tried "smbclient -M <machine>" but doesn't work. I prefer not to use Samba. Thanks. (3 Replies)
Discussion started by: mnagaya
3 Replies

5. Shell Programming and Scripting

error-when trying to send the message thru email.

Hi All, I want to send a message through email. I have written below code. But it is not worling. Anybody has idea, why it is not working?. export $file1=$home1/pip1.$$ mailx -s "This Message from unix" abc@yahoo.com< $file1 thanks,Mary. (5 Replies)
Discussion started by: MARY76
5 Replies

6. UNIX for Dummies Questions & Answers

send message to a remote system

I am analyzing snoop output and want to send "Hello world" to a remote system. I want to see if the message received is encrypted or not. can I use ping to send a text message? like ping "helloworld" <IP Addr> Please help. Thank you (5 Replies)
Discussion started by: rakeshou
5 Replies

7. Red Hat

[help] how to send wall/broadcast message to all clients

Hi, as per title, please help me.. I use command wall host1 host2 hellowwwww but it only receive in the host1.. how can I send this to all the clients.. I want this 1 server to send to all the clients.. or is there any program that I can use? I know this openfire, but seems complicated since... (5 Replies)
Discussion started by: flekzout
5 Replies

8. Programming

[Solved] how to send an integer via message queue?

how can i send an integer via message queue? i try this, but it doesn't work, child process receive 13345943 instead of 5 #include <stdio.h> #include <stdlib.h> #include <sys/types.h> #include <sys/msg.h> #include <sys/ipc.h> #include <sys/sem.h> #include <errno.h> #include <unistd.h>... (2 Replies)
Discussion started by: tafazzi87
2 Replies

9. Post Here to Contact Site Administrators and Moderators

Cannot send new Private Message (PM)

To be able to send PMs your post count must be 10 or greater. You currently have 16 posts. If you have a question for the forum moderators and/or administrators, please post your question here. ...you might want to try searching the forums: What am I doing wrong? (3 Replies)
Discussion started by: -=XrAy=-
3 Replies

10. AIX

Curl, to send text message

hello friends I need to send a text message MSM by AIX with a function called CURL you have some example of how it is done so that you can help me please (4 Replies)
Discussion started by: tricampeon81
4 Replies
REXEC(1)                                                      General Commands Manual                                                     REXEC(1)

NAME
rexec -- remote execution client for an exec server SYNOPSIS
rexec [ -abcdhns -l username -p password ] host command DESCRIPTION
Rexec calls the rexec(3) routine to act as a client for the remote host's rexecd(8) server. It asks that ``command'' be run on the host computer, using username/password authentication. See rexec(3) and rexecd(8) for details of the protocol. OPTIONS
Rexec accepts several options, but only three are likely to be very useful: -l username Set the log-in name on the remote host to username. -p password Provide the password for the remote account. The command line argument will be blanked after being parsed, to prevent it from being seen with ps(1). However, it is still not very secure to type the password on the command line. In particular, be sure that the shell's history file is protected. -n Explicitly prompt for name and password, even if provided in the environment, in the $HOME/.netrc file, or in the environmental variables REXEC_USER and REXEC_PASS. Other options that might be useful with non-standard remote exec daemons, or to debug connections: -a Do not set up an auxiliary channel for standard error from command; the remote standard error and output are then both returned on the local standard output. By default, rexec asks that a separate channel be set up for diagnostic output from the remote command. -b Use signal handling as in BSD rsh(1). Only the signals SIGINT, SIGQUIT, and SIGTERM are echoed to the remote process. They do not remain raised locally, so rexec waits for the remote command to shutdown its side of the socket. Also, CNTRL-Z will only suspend execution locally--the remote command may continue to run. -c Do not close remote standard input when local standard input closes. Normally the standard input to the remote command is closed when the local standard input is closed. -d Turn on debugging information. In particular the command sent to the remote host will be echoed. -h Print a usage message. -s Do not echo signals received by the rexec onto the remote process. Normally, signals which can be trapped are passed on to the remote process; then, when you type CNTRL-C, the remote process terminates as well. USERNAME AND PASSWORD
Rexec(1) searches for the username and password in the following order: 1. If -n is given on the command line, the user will always be prompted for both, even if they are also given on the command line. 2. The command line will be parsed 3. If the environmental variables REXEC_USER or REXEC_PASS are defined, they will define the username or password. 4. The $HOME/.netrc file will be searched. See ftp(1) for a description of this file's format. 5. Finally, the user will be prompted if either the username or password remains undefined. SECURITY
Users of this command should be aware that rexec(3) transmits their password to the remote host clear text, not encrypted. If the network is not secure to the remote host, the password can be comprimised. SIGNALS
Without the -b option, all signals which can be handled are echoed to the remote process. Afterwards, however, they remain raised in the local process. Typically, this means that rexec(1) will exit after receiving a fatal signal, even if the remote process has arranged to handle or ignore it. Differing operating systems use differing signal numbers; for example AIX and SunOS use 18 for SIGTSTP (^Z), while Linux uses 20. There- fore, it may have a different effect remotely than locally. In particular, typing CNTL-Z may not suspend the execution of the remote process. EXAMPLE
rexec othermachine cat ">remote_file; date" <local_file will send local_file to the othermachine as remote_file. BUGS
Please send bug reports, system incompatibilities, and job offers to the author. SEE ALSO
rexec(3), rexecd(8), rsh(1) AUTHOR
Michael Sadd mas22@cornell.edu http://www.tc.cornell.edu/~sadd/ Thanks to Orange Gopher (2/10/97) and Johannes Plass (plass@dipmza.physik.uni-mainz.de, Oct. 17 1996) for useful suggestions. February 14, 1997 REXEC(1)
All times are GMT -4. The time now is 08:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy