Alternative network messaging? Post: 302724977

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...

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. 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...

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

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

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...

LEARN ABOUT OSX

rcp

RCP(1)							    BSD General Commands Manual 						    RCP(1)

NAME

     rcp -- remote file copy

SYNOPSIS

     rcp [-46p] source_file target_file
     rcp [-46pr] source_file ... target_directory

DESCRIPTION

     The rcp utility copies files between machines.  Each source_file, target_file, or target_directory argument is either a remote file name of
     the form ``ruser@rhost:path'', or a local file name (containing no ':' characters, or a '/' before any ':'s).

     The following options are available:

     -4      Use IPv4 addresses only.

     -6      Use IPv6 addresses only.

     -p      Cause rcp to attempt to preserve (duplicate) in its copies the modification times and modes of the source files, ignoring the
	     umask(2).	By default, the mode and owner of target_file are preserved if it already exists; otherwise the mode of the source file
	     modified by the umask(2) on the destination host is used.

     -r      If any of the source files are directories, rcp copies each subtree rooted at that name; in this case the destination must be a
	     directory.

     If path is not a full path name, it is interpreted relative to the login directory of the specified user ruser on rhost, or your current user
     name if no other remote user name is specified.  A path on a remote host may be quoted (using '', '"', or ''') so that the metacharacters
     are interpreted remotely.

     The rcp utility does not prompt for passwords; it performs remote execution via rsh(1), and requires the same authorization.

     The rcp utility handles third party copies, where neither source nor target files are on the current machine.

SEE ALSO

     cp(1), ftp(1), rlogin(1), rsh(1), hosts.equiv(5)

HISTORY

     The rcp command appeared in 4.2BSD.

BUGS

     Does not detect all cases where the target of a copy might be a file in cases where only a directory should be legal.

     Is confused by any output generated by commands in a .login, .profile, or .cshrc file on the remote host.

     The destination user and hostname may have to be specified as ``rhost.ruser'' when the destination machine is running the 4.2BSD version of
     rcp.

BSD
								 October 16, 2002							       BSD