Last three months my syslog file have same messages.

[aamir4u]

I have lot of log messages since last one month.

Dec  8 09:59:15 prodapp1 inetd[12778]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 09:59:15 2011 Dec  8 09:59:29 prodapp1 inetd[12791]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 09:59:29 2011 Dec  8 09:59:35 prodapp1 inetd[12801]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 09:59:35 2011 Dec  8 10:01:35 prodapp1 inetd[12807]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:01:35 2011 Dec  8 10:03:35 prodapp1 inetd[12817]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:03:35 2011 Dec  8 10:04:17 prodapp1 inetd[12826]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 10:04:17 2011 Dec  8 10:04:30 prodapp1 inetd[12843]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 10:04:30 2011 Dec  8 10:05:35 prodapp1 inetd[12950]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:05:35 2011 Dec  8 10:07:35 prodapp1 inetd[12955]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:07:35 2011 Dec  8 10:09:19 prodapp1 inetd[12985]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 10:09:19 2011 Dec  8 10:09:30 prodapp1 inetd[12998]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 10:09:30 2011 Dec  8 10:09:35 prodapp1 inetd[13008]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:09:35 2011 Dec  8 10:11:35 prodapp1 inetd[13014]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:11:35 2011 Dec  8 10:13:35 prodapp1 inetd[13020]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:13:35 2011 Dec  8 10:14:21 prodapp1 inetd[13026]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 10:14:21 2011 Dec  8 10:14:31 prodapp1 inetd[13039]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 10:14:31 2011 Dec  8 10:15:35 prodapp1 inetd[13047]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:15:35 2011 Dec  8 10:17:35 prodapp1 inetd[13058]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:17:35 2011 Dec  8 10:19:23 prodapp1 inetd[13062]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 10:19:23 2011 Dec  8 10:19:31 prodapp1 inetd[13076]: registrar/tcp: Connection from localhost (127.0.0.1) at Thu Dec  8 10:19:31 2011 Dec  8 10:19:35 prodapp1 inetd[13086]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:19:35 2011 Dec  8 10:21:35 prodapp1 inetd[13184]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:21:35 2011 Dec  8 10:23:35 prodapp1 inetd[13191]: registrar/tcp: Connection from prodapp1 (192.168.4.7) at Thu Dec  8 10:23:35 2011

What it is mean is any thing critical.

[Dennis Handly]

>What it is mean is any thing critical?

Please edit your post to format it correctly so we can read it.

[Henry Fauni]

These are normal EMS messages.

[aamir4u]

Spoiler

Sorry ,

Please see the attached file

Please tee me is any thing critical on my log messages because every day  many same log generated  in my syslog file.what is this files mean and how can solved that problem.

Please see it

[rariasn]

Hi:

By default, inetd starts with connection logging disabled.
If no inetd is running, the -l option causes the inetd to start with connection logging enabled.

# ps -ef |grep -i inetd

root  1908     1  0  Nov 22  ?         1:56 /usr/sbin/inetd -l

For supress this messages:

# inetd -k

# inetd

Verify /etc/rc.config.d/netdaemon file

export INETD_ARGS="-l"

change to:

export INETD_ARGS=""

rgs,

.

[rariasn]

Hi Aaamir:

Disable inetd loggin.

# inetd -k;inetd

Verify "syslog" file.

Dec 27 10:32:28 minerva inetd[24128]: Going down on signal 15
Dec 27 10:32:28 minerva inetd[25081]: Reading configuration
Dec 27 10:32:28 minerva inetd[25081]: ftp/tcp: Added service, server /usr/lbin/ftpd
Dec 27 10:32:28 minerva inetd[25081]: telnet/tcp: Added service, server /usr/lbin/tcpd
Dec 27 10:32:28 minerva inetd[25081]: dtspc/tcp: Added service, server /usr/dt/bin/dtspcd
Dec 27 10:32:28 minerva inetd[25081]: recserv/tcp: Added service, server /usr/lbin/recserv
Dec 27 10:32:28 minerva inetd[25081]: ctmagent/tcp: Added service, server /home/ctmagpre/ctm/exe/p_ctminetd
Dec 27 10:32:28 minerva inetd[25081]: registrar/tcp: Added service, server /etc/opt/resmon/lbin/registrar
Dec 27 10:32:28 minerva inetd[25081]: omni/tcp: Added service, server /opt/omni/lbin/inet
Dec 27 10:32:28 minerva inetd[25081]: rpc.cmsd/udp: Added service, server /usr/dt/bin/rpc.cmsd
Dec 27 10:32:28 minerva inetd[25081]: Thru with configuration
Dec 27 10:32:28 minerva inetd[25081]: Configuration complete

rgs,

[aamir4u]

How can restart that paricular daemon again.inetd

Thanks.

[Dennis Handly]

>How can restart that paricular daemon?

As rariasn said, you can kill and restart: inetd -k; inetd

Or you can just toggle the logging: inetd -l