Though creating configuration files is not difficult, it takes time and some
research. Since xinetd is not really the *NIX standard, using the non-standard
daemon really should command the addition of more configuration files.they
should be present for the servers that people use... CVS for example. Sure,
disable them but still have the config files there.
Created attachment 43956 [details]
cvs pserver xinetd configuration file (/etc/xinetd.d/cvspserver)
Note that the configuration file I submitted is enabled despite what the default
says. I am simply submitting what I am currently running.
For the configuration file I specified to be of any use a cvsroot needs to exist
with proper permissions. Bug 59045 for cvs brings that separate issue up. Might
be debatable as to whether or not this bug should be dependent on 59045, but
I'll do it anyways.
If such a file should be added (I don't think it's a good idea, too much
configuration in the file), it should be added to cvs, not xinetd.
*** This bug has been marked as a duplicate of 136929 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.