[Sudoscript-devel] 2.0 Architecture

[Howard O. <hb...@eg...>]

Tommy Smith from Eatel suggested that I consider running a
log-per-session with sudoscript. This struck me as a very good
idea for several reasons. First and foremost, it provides a way to
uniqely identify a particular session's output. Rather than
multiplaxing all sessions through a single typescript FIFO, we
could provide a FIFO per session, and thus a log per session.
A second benefit is that the master sudscriptd could provide traffic
cop functions, cleaning up after defunct sessions. Finally, the
master daemon could use syslog to track session startup and shutdown.
(I've been reluctant to use syslog so far because of the huge
quantity of data that can be produced.)

I've drawn up an architecture to implement these ideas. It's
available at http://www.egbok.com/sudoscript/new_arch.gif.
I have  90% of an implementation done in Perl, too. One thing
I want to consider is a rewrite of sudiscriptd in C. I'm
concerned that the overhead associated with the Perl interpreter
will start to get significant when more than a few users are active
on a single system.

Comments and suggestions are very welcome!

Howard Owen                    "Even if you are on the right
EGBOK Consultants               track, you'll get run over if you
hb...@eg...  +1-650-339-5733  just sit there." - Will Rogers