11-01-2012
xinetd/inetd/u_inetd are more tcp related, for independent services, so 1) you would have to worry about parallel operation and 2) the overhead per message is high unless the protocol maintains the connection for many messages.
The beauty of a UDP socket receiver is that one socket on one server serves all clients, first-come, first-served, without locking, accept, fork or connection setup overheads. If you use a broadcast address, you could have parallel servers on every host with a client making a local message log.
This User Gave Thanks to DGPickett For This Post:
6 More Discussions You Might Find Interesting
1. Programming
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
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
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
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
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
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
LEARN ABOUT LINUX
if.conf
NETSCRIPT-2.2.conf(5) File Formats Manual NETSCRIPT-2.2.conf(5)
NAME
/etc/netscript/network.conf - interface, firewalling, and QoS configuration file.
/etc/netscript/if.conf - interface setup shell script file
/etc/netscript/qos.conf - QoS setup shell script file
/etc/netscript/ipfilter.conf - IP chains filtering shell script file
/etc/netscript/srvfilter.conf - server IP filter shell script file
DESCRIPTION
This manpage is a place holder until something better is written when the netscript itself has stopped changing rapidly.
Please see the README file in the /etc/netscript directory, and READ the configuration files if you need to change them. Apart from net-
work.conf, all of them contain sh (1) shell script functions which are there so that various things can be altered or hooked in at the
right place. Network.conf contains the full network setup details, including special interface setup for the likes of ciped/pppd/wanconfig,
and is fully commented with examples given.
UPGRADE PATH FROM KERNEL 2.2.X
The firewall/IP filtering stuff in ipfilter.conf is the part that changed radically with the move to iptables and a far better way of set-
ting up the IP filtering rules, however the QoS and interface startup/shutdown in if.conf have changed but are backwards compatible with
the old 2.2.x ipchains version of netscript for the interface address configuration settings. You will have to set up the filtering again
to use iptables by directly using the iptables commands.
Also, the kernel 2.2.x version scripts are set up so that iptables is only run on a 2.4.x kernel, otherwise IP forwarding is disabled if
beforehand you set IPFWDING_KERNEL to FILTER_ON in network.conf.
This means that when you upgrade a box to a 2.4.x router kernel, you should then be able to reboot it and log into remotely and upgrade
netscript to the version that will support 2.4.x. In this situation, if you have set old IPFWDING_KERNEL setting to FILTER_ON beforehand
in network.conf, all IP forwarding through the box will also be disabled. This means that you can safely remotely upgrade a firewall.
SEE ALSO
netscript(8), ipchains(8), iproute(8), brcfg(8).
AUTHOR
This manual page was written by Matthew Grant <grantma@anathoth.gen.nz>, for the Debian GNU/Linux system (but may be used by others).
BUGS
The author is lazy. He needs to write btter man pages...
November 23, 2000 NETSCRIPT-2.2.conf(5)