Roger Leigh <[email protected]> writes: > The initial work that needs doing is defining a suitable file format. A > simple key=value or Key: Value scheme would probably be sufficient if > there's only one service per file. Alternatively, the xinetd format is > /currently/ the superset, but that's perhaps not flexible enough for the > future since we're then tied into being compatible with that single > implementation.
I'd love to see a solution that would involve packages shipping xinetd fragments and stripping those fragments down for inetd if inetd were in use instead. The xinetd syntax is more expressive and is used by other distributions, so we wouldn't be inventing something new that's specific to Debian. And then xinetd wouldn't have to go through update-inetd and could just use the fragments directly, which would resolve that integration problem in what I think is a cleaner way. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
