[Bucardo-general] Question about NON-UNIX systems support.

[Greg Sabino Mullane]

> I would like to know, what parts of Bucardo could be a problem for using 
> Bucardo on a NON-UNIX system?
> Which part of the code I should look like and eventually change if I 
> want to make a windows port?
> Also, has someone tested Bucardo on Mac OS? Does it works?

I don't know about OS X, but it has been tested on some flavors of BSD.

As far as Windows, the immediate problem parts I can think of are setsid() in
bucardo_ctl, the forking in Bucardo.pm, being careful about the paths, and the
kill calls (including the kill 0). Some of which may actually work on Windows
these days, I honestly don't know, as I rarely venture into Win32 land.

All the Perl modules will need to work, of course, but strawberry perl should
make that a lot easier. Sys::Syslog could be problematic.

Keep in mind that all of this is only for running *the Bucardo daemon itself*.
Bucardo could happily live on a small Linux box and replicate things between any
number of Windows boxes (or even a mixture of Windows and Unix)

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 226 bytes
Desc: OpenPGP digital signature
Url : https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20090422/0d21046a/attachment.bin