Michael Holzt <[EMAIL PROTECTED]> writes: >> c) run nnrpd from inetd. > > This is not possible without the use of a secondary ip address.
Or running innd on port 433 and coordinating that with your peers and then running nnrpd on port 119 out of xinetd or the like, which is really a better solution all around except for the peer coordination. innd invoking nnrpd on MODE READER is really a hack and causes various bits of strangeness. The overhead of building nnrpd with SSL support should be relatively minor, since the SSL libraries will be shared between all of the nnrpd processes, but I haven't measured it. > I'm afraid it does. > > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > root 8876 0.0 0.4 30648 2276 pts/4 S+ 21:48 0:00 - nnrpd-ssl > root 8877 0.0 0.2 22420 1516 pts/3 S+ 21:48 0:00 - nnrpd These numbers are unfortunately not horribly meaningful. It's really difficult to extract from Linux the real memory consumption per process; RSS doesn't subtract out shared pages (at least, last time I checked). -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
