log file for services

[Ron Bromwell]

When the services in /etc/inetd.conf start at boot up, is information about these services logged anywhere? if so, where would I find it?

Ron

[Massimo Bianchi · Accepted solution]

Hi,
you find all the information in /var/adm/syslog/sysglog.log

do a

grep inet /var/adm/syslog/sysglog.log


and search for "Added Service"

Massimo

[Ken Hubnik_2]

From the man pages.

In such
cases, inetd refuses the connection from the same service invocation
five times. This is visible in the system log if inetd connection
logging and syslogd logging for the daemon facility are both enabled
(see syslogd(1M)).
-l 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. Otherwise the -l
option causes inetd to send the signal SIGQUIT to the inetd
that is already running, which causes it to toggle the state
of connection logging.

[RolandH]

Yes it is logged in /var/adm/syslog/syslog.log.

And it looks like this

....
Jun 3 15:35:26 polonium inetd[1353]: shell/tcp: Added service, server /usr/lbin
/remshd
Jun 3 15:35:26 polonium inetd[1353]: spc/tcp: Added service, server /usr/bms/bi
n/softspcd
Jun 3 15:35:26 polonium inetd[1353]: telnet/tcp: Added service, server /usr/lbi
n/telnetd
Jun 3 15:35:26 polonium inetd[1353]: time/udp: Added service, server internal
Jun 3 15:35:26 polonium inetd[1353]: time/tcp: Added service, server internal
Jun 3 15:35:26 polonium inetd[1353]: rpc.cmsd/udp: Added service, server /usr/d
....

look at the beginning of syslog.log

HTH

Roland

[Suresh Patoria]

Hi,

by default services of /etc/inetd.conf logs store in /var/adm/syslog/syslog.log file

for all the services trace the log u have to enable the logging service inetd daemon using command

inetd -l

it will enable the logging service

Thanx

[Ron Bromwell]

the log shows the services as added, but when i preform a ps -ef and grep on the service it does not show up. Is there someplace else I could look.

[Alzhy]

Rom,

INETD is your "super-daemon" that controls startup of "server" programs on a UNIX host's end. Along with /etc/services - it serves as a director which "service" needs to be launched based on the properties of the connection -- ie. tcp or udp.. and the port number.

If you want explicit logging of when these listed services in /etc/inetd are called and from where -- you can use TCP wrappers (or the tcpd) program. By the use of "tcp wrappers" you can log and control who has acccess to which services and makes your system a little bit secure... Most newer inetd programs already incorporate the features of tcp wrappers.

[RolandH]

Hi ron,

the service will start if you need it. So start a telnet session to your system and then grep for telnetd.
Ot start a ftp session to your system and then grep for the ftpd. You will see it is running.


HTH
Roland

[Alzhy]

And by the way Rom, you will not be able to "see" via ps|grep ALL the services as these "services" will only be active when there is a connection to them .. ie. telnetd, ftpd, etc...

If you install TCP wrappers and explicit logging (you may tweak your syslog.conf so you control system logging...) - you may monitor inetd connections by doing a:

telnet

[Patrick Wallek]

In a nutshell, if a service is defined in /etc/inetd.conf and /etc/services, it will not be started by the inetd daemon until it is needed. You will never see an FTP process on your system unless someone is actively doing an FTP to your system.