Sponsored Content
Top Forums Shell Programming and Scripting Alternative network messaging? Post 302724961 by 123_abc on Thursday 1st of November 2012 01:40:12 PM
Old 11-01-2012
Unfortunately, I have to use rcp, but all R-services are TCP-based :-(

If multiple users sent files at the same time, the server would have to provide one socket for each incoming request, which would cause a lot of server load. Maybe I could use only one socket, but with some kind of semaphore?
 

6 More Discussions You Might Find Interesting

1. Programming

Instant Messaging App Help

I was hoping someone could assist me on a text-based instant messaging client(using UDP) I am working on. I have the network communication basics already in place but, specifically, needed some further help on the "messaging other users" and "getting a user list" functions. The server code that... (0 Replies)
Discussion started by: AusTex
0 Replies

2. IP Networking

DT messaging could not be started

this id the message i get with a suggestions to check those files: /etc/src.sh /etc/hosts /usr/adm/inetd.sec i have little knowledge of hoe to edit those files/ i went to the etc library and didn't found src.sh file. what should i do? also didn't find the inetd.sec file In the host... (3 Replies)
Discussion started by: amirp
3 Replies

3. UNIX and Linux Applications

how do i enable messaging

hi guyz i work as a system administrator for some organization(am a newbie). one of the solaris machines is loaded with the messenger server...all configured by a former administrator. my task was to create user accounts for the mail and calendar services and as i checked its not working .....i... (0 Replies)
Discussion started by: henokia4j
0 Replies

4. Programming

problems while using messaging queues....

hi I am using posix functions such as mq_open, mq_close and including the mqueue.h. but its giving a linking error,"undefined reference to mq_open and mq_close". it it that we have to link some library or so while compiling... plzzz help Thanxs Mohit (0 Replies)
Discussion started by: mohit3884
0 Replies

5. UNIX for Advanced & Expert Users

The DT messaging system could not be started

Hello All, I am getting " The DT messaging system could not be started" message when wants to login as root on a box running on tru64 5.1A. /etc/hosts is ok. when i see in .dt/errorlog it shows message server could not be started. Thanks for help. Awadhesh (2 Replies)
Discussion started by: Awadhesh
2 Replies

6. Shell Programming and Scripting

The DT messaging system could not be started.

Good Morning, Users can no longer log into SunBlade 2500 Solaris 9 system (though root still can). Here's what I'm getting and what I've done. I'm most suspicious of the full drive since that pops up twice and I did see one looks full. What's a good way to reduce what's on it?- or.. what else... (2 Replies)
Discussion started by: Stellaman1977
2 Replies
writesrv(8)						      System Manager's Manual						       writesrv(8)

NAME
writesrv - Lets users send messages to and receive messages from a remote system. SYNOPSIS
/usr/sbin/writesrv DESCRIPTION
The writesrv daemon allows users to send messages to users on a remote system, and to receive responses from users on a remote system with the write command. The writesrv command receives incoming requests from a write command and creates a server process to handle the request. This server process communicates with the client process (write) and provides whatever services are requested. To perform these services, the writesrv daemon creates a socket on the port defined in the /etc/services file. All requests for service go as messages to this socket. STARTING AND STOPPING writesrv. You can cause the writesrv daemon to be started during system boot with /sbin/init.d/write. The writesrv daemon starts automatically if the WRITESRV variable is defined properly in /etc/re.config. To start writesrv automatically during system boot, do the following as superuser. rcmgr set WRITESRV yes To prevent writesrv from starting automatically during system boot, do the following as superuser: rcmgr set WRITESRV no By default, writesrv is not set and therefore /usr/sbin/writesrv does not run. You can start the writesrv daemon manually as follows: /sbin/init.d/write start You can stop writesrv manually as follows: /sbin/init.d/write stop NOTES
If the writesrv daemon terminates abnormally (that is, for a system crash, a power failure, or the kill -9 command), someone must manually clean out the /usr/spool/writesrv directory to remove any files left behind. RELATED INFORMATION
Commands: write(1) Files: services(4) delim off writesrv(8)
All times are GMT -4. The time now is 01:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy