Sponsored Content
Top Forums UNIX for Advanced & Expert Users 3600 tcp/udp, trap-daemon, text relay-answer Post 54442 by cassj on Friday 13th of August 2004 10:01:55 PM
Old 08-13-2004
3600 tcp/udp, trap-daemon, text relay-answer

3600 tcp/udp, trap-daemon, text relay-answer

Does anyone know what this service is responsible for, or how significant it is?

Thanks.....James
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

TCP/UDP Ports

Just starting to work with unix, wondering if there is any good on-line documentation explaining TCP/UDP ports, how to use them, etc... Thanks.... (1 Reply)
Discussion started by: eugene_mayo
1 Replies

2. IP Networking

TCP/UDP Ports

Just wondering if anyone knows of any good on-line documentation on TCP/UDP Ports. Basically i want to know how to check if they are in use, learn how to close them, etc... Thanks... (5 Replies)
Discussion started by: eugene_mayo
5 Replies

3. UNIX for Dummies Questions & Answers

Urgent answer needed, please: help with a text editor

I'm sorry if this has been posted before, but I'm in a big hurry and I need a pretty quick answer: I have to make a project for school which consists of many BASH scripts. At school we have Sun Sparcs. During the laboratory hours I used to open the text editor (in the graphics interface), edit the... (4 Replies)
Discussion started by: MtFR
4 Replies

4. UNIX for Dummies Questions & Answers

How to check the TCP/UDP port of a connection

Hi, Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in? Regards, Tayyab (2 Replies)
Discussion started by: tayyabq8
2 Replies

5. HP-UX

3600 C Class disk upgrade

Hi there I have a 3600 C class PA-RISC workstation, and I am wondering if I can increase the disk capacity on it. I have a couple of 73GB Seagate SCSI disks which I could fit in to the SCA slots, and if they are not suitable I am willing to find alternatives - but I am not sure how to go... (3 Replies)
Discussion started by: Freddo_21
3 Replies

6. Infrastructure Monitoring

linux snmp trap relay

Hi all, I'm after a linux utility that can relay all incoming traffic on a certain port to another server. Can anyone recommend a good program? I've taken a look at snmptrapd, but it's not obvious how this can be configured for my requirements. Many thanks. (1 Reply)
Discussion started by: badoshi
1 Replies

7. IP Networking

UDP Server/Daemon for receiving & acknowledging data

I'm looking for a couple high level pointers to writing a UDP server that will be acknowledging data at a rate of approximately twelve packets every second and will be running on and older but more or less dedicated Solaris 9 box. Acknowledging the data packets is relatively simple, after... (2 Replies)
Discussion started by: allbread
2 Replies

8. UNIX for Advanced & Expert Users

bind 9 forwarders: use UDP or TCP?

I use forwarders for a subzone, but TCP 53 is blocked, So does forwarders really need TCP? If forwaders use UDP, I can't get following scenario to work: main zone is master, but subzone is forwad. Is it possible? (On name sever itself, resolution of xx.stub.abc.com worked fine.) #sub zone... (2 Replies)
Discussion started by: honglus
2 Replies

9. AIX

TCP/UDP port range for default AIX NFS?

May I know what is the TCP/UCP port range for any default AIX NFS? Based on rpcinfo -p, I got the following output: program vers proto port service 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100000 4 ... (4 Replies)
Discussion started by: famasutika
4 Replies
inetd.conf(4)						     Kernel Interfaces Manual						     inetd.conf(4)

NAME
inetd.conf, inetd.conf.local - The default configuration files for the inetd daemon SYNOPSIS
The default configuration file for all cluster members is: /etc/inetd.conf The configuration file for a specific member in a cluster is: /etc/inetd.conf.local The inetd.conf.local file is a Context-Dependent Symbolic Link (CDSL) and must be maintained as such. See the System Administration manual for more information. DESCRIPTION
If the inetd daemon is started without specifying an alternate configuration file, the inetd daemon reads the inetd.conf file and inetd.conf.local file, in this order, for information on how to handle Internet service requests. For this reason, if an entry exists in both configuration files, the entry in /etc/inetd.conf.local overrides the entry in /etc/inetd.conf. The inetd daemon reads its configuration files only when the inetd daemon starts or when the inetd daemon receives a SIGHUP signal. Each line in theinetd configuration files defines how to handle one Internet service request. Each line is of the form: ServiceName SocketType ProtocolName Wait/NoWait UserName ServerPath ServerArgs (Note: The backslash and the continuation of information on to a second line is for display purposes only. In the configuration file, the entries appear on a single line.) These fields must be separated by spaces or tabs. Continuation lines are terminated with a (backslash). Comments are denoted with a # (number sign). The fields have the following meanings: Specifies the name of an Internet service defined in the /etc/services file. For services provided internally by the inetd daemon, this name must be the official name of the service. That is, the name must be identical to the first entry on the line that describes the service in the /etc/services file. Specifies the name for the type of socket used for the service. You can use either the stream value for a stream socket, the dgram value for a datagram socket, the raw value for a raw socket, the rdm value for a reliably delivered message socket, or the seqpacket value for a sequenced packet socket. You can also use xstream and xdgram to permit the transparent mode of connections for stream and datagram sockets, respectively. Currently, only applica- tion gateways for firewall services use the transparent mode of connection. Specifies the name of an Internet protocol defined in the /etc/protocols file. For example, use the tcp value for a service that uses the TCP/IP protocol and the udp value for a service that uses the UDP protocol. When you use a tcp or udp value, inetd creates AF_INET sockets; this is the default behavior. If you want inetd to create AF_INET6 sockets, use the tcp6 or udp6 value. The inetd daemon maps these values to the tcp and udp protocol names internally. For RPC services the field consists of the string rpc followed by a slash (/) and one of the following: An asterisk (*) One or more nettypes One or more netids A combination of nettypes and netids If you specify an invalid nettype, it is treated as a netid. For example, if you specify rpc/*, it specifies the service uses all the transports supported by the system. Contains either the wait or the nowait instruction. For datagram servers, specify wait. This instructs the inetd daemon to wait for a datagram server to read at least one datagram from the socket before exiting. Single- threaded datagram servers process all incoming datagrams, then they time out (for example, comsat, biff, and talkd). Multithreaded datagram servers read one datagram from the socket, create a new socket, then fork and exit (for example, tftpd). For servers using stream sockets, specify nowait for multithreaded servers. This instructs inetd to accept connection requests and pass a newly accepted socket that is connected to the client of the service to the server. Specify wait for single-threaded servers. This instructs inetd to pass the listening socket to the server and wait. The server must accept at least one connection request before exiting. Specifies the username that the inetd daemon should use to start the server. This variable allows a server to be given less permission than root. Specifies the full pathname of the server that the inetd daemon should execute to provide the service. For services that the inetd daemon provides internally, this field should be internal. If you want to disable this service, this field should be disable in the /etc/inetd.conf.local file. Specifies the command line arguments that the inetd daemon is to pass to the server specified in ServerPath. The arguments to ServerPath should be just as they normally are, starting with the name of the program. For services that the inetd daemon provides internally, this field should be blank. EXAMPLES
The following are sample entries in the /etc/inetd.conf file for an inetd daemon that: Uses the ftpd daemon for servicing ftp requests on an AF_INET6 socket Uses the talkd daemon for ntalk requests on an AF_INET socket Provides time requests internally on AF_INET6 sockets ftp stream tcp6 nowait root /usr/sbin/ftpd ftpd ntalk dgram udp wait root /usr/sbin/talkd talkd time stream tcp6 nowait root internal time dgram udp6 wait root internal How you enable and disable services in a cluster depends on the number of cluster members. The following two examples show the same clus- ter that has three members (0, 1, and 2), but shows two diferent methods to accomplish the same goal. Choose the method most suitable to your cluster environment. If you want to enable the ftpd daemon on all cluster members except member 2, do the following: To enable the ftpd daemon for all members, enter the following in the /etc/inetd.conf file: ftp stream tcp nowait root /usr/sbin/ftpd ftpd To disable the ftpd daemon for member 2, enter the following in the /etc/inetd.conf.local for member 2: ftp stream tcp nowait root disable If you want to disable the ftpd daemon on all cluster members (the whole cluster), but enable it on members 0 and 1, do the following: To disable the ftpd daemon by default for the whole cluster, enter the following in the /etc/inetd.conf file: #ftp stream tcp nowait root /usr/sbin/ftpd ftpd To enable the ftpd daemon for member 0, enter the following in the /etc/inetd.conf.local file for member 0: ftp stream tcp nowait root /usr/sbin/ftpd ftpd To enable the ftpd daemon for member 1, enter the following in the /etc/inetd.conf.local file for mem- ber 1: ftp stream tcp nowait root /usr/sbin/ftpd ftpd Member 2 does not have an ftpd entry in its /etc/inetd.conf.local file. Therefore, the ftpd daemon is not started. RELATED INFORMATION
Commands: biff(1), comsat(8). Daemons: inetd(8), talkd(8), tftpd(8). Files: protocols(4), services(4). delim off inetd.conf(4)
All times are GMT -4. The time now is 06:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy