CVS update: samba/source/msrpc (fwd)

Luke Kenneth Casson Leighton lkcl at
Fri Jan 21 20:09:05 GMT 2000

> > yehh... so as long as i make the code reentrant (code review needed!)
> > everyone should be happy.
> Well yes. But the most important requirement is that SMBDs pass the
> DCE/RPC calls to a master process for each DCE/RPC service.

um... that's what the idea of the unix-domain socket is for.  in fact,
what i want to do is to have one daemon be capable of listening to
_multiple_ unix-domain sockets.

i made a mistake by having one daemon per socket: i actually wanted to
create servicesd which deals with \PIPE\srvsvc, \PIPE\wkssvc and
\PIPE\browsess because they're really trivial.

> That allows
> each DCE/RPC service code author to choose the implementation
> (fork()ing, async, threaded). You can choose to fork() today and a year
> from now clean up the code to be reentrant and convert it to async.

> As for writing reentrant code, the single most important rule to keep in
> mind "avoid statics and globals for storing call-specific state". Pass
> around the state as a function argument.


More information about the samba-technical mailing list