If seems to me that what is wanted here is a "superfinger" daemon, a sort of mini-inetd. It would accept the connection from inetd, make a decision based upon some set of system or per-user configuration files as to which finger daemon should be spawned, and then hand the connection to the appropriate finger daemon.
This seems like a bit of work, honestly. Finger daemons are easy to write, so they have often provided egregious security vulnerabilities. Given that history, I am not sure this is such a good idea, anyway. -- Mike On 2000-05-22 at 09:25 +0200, Radovan Garabik wrote: > Unlike for ftpd or httpd, Conflict is appropriate here.
