[Buildbot-devel] Testing a client-server system

[Brad Hards]

On Monday 09 March 2009 10:43:14 am you wrote:
> I don't have a remote clue. I'm pretty sure that one can start up samba as
> a daemon and get log files. Starting samba and keeping it running while
> watching stdout could be possible, but you'd have to fake the end of the
> process. That would probably require you to hack a buildbot slave command.
It can definitely go into daemon mode. 

My problem is really that I want to make sure the server (in daemon or 
interactive mode) is ready. So I need to observe the output. I hadn't thought 
about a separate log file - I was trying to get the log from buildbot, and I 
can't see how to get the log from a previous buildstep.

Alternatively, if I can fake the end of the process, that would be OK. I'd 
need a hint about that too - is it OK to just call mystep.commandComplete() 
from the log observer?

> Daemon and log parsing sounds more straightforward. As straightforward as a
> "sudo" on a slave could be. If I knew samba even remotely, I'd give you an
> educated statement on how scary I think that is. ;-)
Worried me too :-)

The slave is only able to sudo the minimum required commands, and the samba 
server doesn't have the fileserver module loaded (just my exchange modules). 
Also, the server is only accessible on the slave (no outside access, by 
firewall rules).


Brad