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
KCM(8)							    BSD System Manager's Manual 						    KCM(8)

NAME
kcm -- process-based credential cache for Kerberos tickets. SYNOPSIS
kcm [--cache-name=cachename] [-c file | --config-file=file] [-g group | --group=group] [--max-request=size] [--disallow-getting-krbtgt] [--detach] [-h | --help] [-k principal | --system-principal=principal] [-l time | --lifetime=time] [-m mode | --mode=mode] [-n | --no-name-constraints] [-r time | --renewable-life=time] [-s path | --socket-path=path] [--door-path=path] [-S principal | --server=principal] [-t keytab | --keytab=keytab] [-u user | --user=user] [-v | --version] DESCRIPTION
kcm is a process based credential cache. To use it, set the KRB5CCNAME enviroment variable to 'KCM:uid' or add the stanza [libdefaults] default_cc_name = KCM:%{uid} to the /etc/krb5.conf configuration file and make sure kcm is started in the system startup files. The kcm daemon can hold the credentials for all users in the system. Access control is done with Unix-like permissions. The daemon checks the access on all operations based on the uid and gid of the user. The tickets are renewed as long as is permitted by the KDC's policy. The kcm daemon can also keep a SYSTEM credential that server processes can use to access services. One example of usage might be an nss_ldap module that quickly needs to get credentials and doesn't want to renew the ticket itself. Supported options: --cache-name=cachename system cache name -c file, --config-file=file location of config file -g group, --group=group system cache group --max-request=size max size for a kcm-request --disallow-getting-krbtgt disallow extracting any krbtgt from the kcm daemon. --detach detach from console -h, --help -k principal, --system-principal=principal system principal name -l time, --lifetime=time lifetime of system tickets -m mode, --mode=mode octal mode of system cache -n, --no-name-constraints disable credentials cache name constraints -r time, --renewable-life=time renewable lifetime of system tickets -s path, --socket-path=path path to kcm domain socket --door-path=path path to kcm door socket -S principal, --server=principal server to get system ticket for -t keytab, --keytab=keytab system keytab name -u user, --user=user system cache owner -v, --version Heimdal May 29, 2005 Heimdal
All times are GMT -4. The time now is 03:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy