My understanding of inetd and inetd.conf is that the entries in
inetd.conf tell inetd what processes to start when it receives
connection requests on the corresponding ports.
Now a collegue of mine tells me that as soon as inetd is started it
spawns a number of processes simply because corresponding entries are
in inetd.conf.
The entries are like the following:
myApp stream tcp nowait myusr /mypath/myApp myapp
<myargs>
Is that possible?
What is it that I don't understand about how inetd uses inetd.conf?
Thanks,
--Ulf