On Fri, 27 Feb 2004, Renaud Deraison wrote: > Anyway, the client - server communication induces very little overhead, > except when the client logs in. The communication protocol uses little > CPU, and if you want to save CPU cycles, you can always compile nessusd > and the client so that they use a unix socket and therefore don't use > SSL nor TCP/IP. > > ./configure --enable-unix-socket=/usr/local/var/nessus/nessusd.socket
Client-server communication over a unix socket uses quite a lot of CPU because recv_line() on a non-SSL connection reads single bytes (e.g. there is one syscall per every received byte). Ironic, isn't it? I must look at the buffering patch Michel announced recently. It might have fixed it...or provided sufficient "infrastucture" to make the fix trivial. --Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ] "Resistance is futile. Open your source code and prepare for assimilation." _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
