On 18 March 2002, Nick Fisher said:
> 1) SA Doesn't work Win32
> Line 649 of SpamAssassin.pm (2.11) has getpwuid on it. This appears to be
> getting the user's home directory but I don't know why. I've hacked it to
> return something but I'd love to know why it's doing this so I can write a
> propper patch. Once that is hacked it's just a little slow. I also can't get
> the makefile to work.
Without looking at the code, I would guess SA needs getpwuid to find the
user's SA directory, ~/.spamassassin on Unix. This is where the
auto-whitelist and user_prefs file live on Unix.
I suppose the properly Microsoftish thing is to put something in the
registry, but you're the Windows guy around here.... ;-)
> 2) SA is *SLOW* on Win32
> When you fireup SA it takes quite some time to start. Once it's going it
> preforms all right. I think this has to do with the overhead of perl.exe
> starting.
SA is slow to startup everywhere. On Unix, we have spamd, which starts
up once (boot time, presumably) and then sits in the background handling
requests to process a message from spamc. I very much doubt that a Unix
daemon would work as-is on Windoze, though.
It sounds like SA's other performance problems -- ie. the time it takes
to process a message once the startup overhead is gone -- will be
addressed, at least partially, in SA 2.2.
Greg
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
