Page MenuHomeFreeBSD

inetd: Add examples from manual page and other sources
Needs ReviewPublic

Authored by debdrup on Tue, Feb 23, 9:36 AM.

Details

Reviewers
None
Group Reviewers
manpages
Summary

The manual page lists a bunch of examples, some of which already exist
in this file. Since it's both easier to remember when all examples are
listed in the same location, move examples so they get installed into
/etc/inetd.conf

This also means users won't have to copy-paste, but can simply
uncomment one or more services to use them.

As such, it also becomes necessary to remove the examples from the
manual page, so instead add a note explaining where the previous
examples as well as others may be found.
Cross-references, including to ports, have also been added where
applicable.

The rsync example has lived in the bug tracker for too long,
considering how useful it can situationally be, for example when
backup jobs on client devices are run through periodic(8) weekly.

The microsoft-ds entry is necessary for Windows 10 compatibility
(this can be confirmed with packet capturing, as it is not readily
documented at time of writing).

While here, remove two examples for which compatible daemons could not
be found in ports.

Submitted by: David Yeske <dyeske at gmail.com> (in part, prev ver)
PR: 122037

Test Plan

Igor and mandoc; both passed for lines modified

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint OK
Unit
No Unit Test Coverage
Build Status
Buildable 37354
Build 34243: arc lint + arc unit

Event Timeline

Just being curious, what's the benefit of running rsyncd through inetd instead of using its standalone daemon?

Just being curious, what's the benefit of running rsyncd through inetd instead of using its standalone daemon?

The main advantage of inetd is that it starts a daemon only when a request comes in.

For rsyncd, smbd, prometheus_sysctl_exporter, et al., if the client machines have a weekly rsync job, or if prometheus only probes every 5 minutes, or only the occational connection via SMB is made - it makes more sense to only start them when they're needed.

Naturally, if you're constantly doing persistent samba sharing, 10-second to 2 minute probes with prometheus, or constant rsync backup jobs over the net, running the daemon via a rc script makes more sense.

The main advantage of inetd is that it starts a daemon only when a request comes in.

For rsyncd, smbd, prometheus_sysctl_exporter, et al., if the client machines have a weekly rsync job, or if prometheus only probes every 5 minutes, or only the occational connection via SMB is made - it makes more sense to only start them when they're needed.

This sounds fair to me. I'm fine with adding them.

usr.sbin/inetd/inetd.conf
123

I'm not sure if this is needed to add this, but we don't have if_wg(4) manpage.

debdrup retitled this revision from inetd.conf: Add entries for Samba sharing and rsyncd to inetd: Add examples from manual page and other sources.Wed, Feb 24, 8:21 PM
debdrup marked an inline comment as done.

Rework review to address outstanding issues with examples

Also fix reference to wg(4) which was mistakenly referred to by if_wg(4)

debdrup edited the test plan for this revision. (Show Details)
debdrup edited the summary of this revision. (Show Details)