Why is pyzor running as root? ----- Original Message ----- From: Justin Mason To: Warren Togami Cc: Mark Martinec ; SpamAssassin Dev Sent: Friday, December 18, 2009 4:07 PM Subject: Re: pyzor error during spamd startup
it should be harmless, btw, since this is just the preloading-modules step. Ugly, though. On Fri, Dec 18, 2009 at 20:53, Warren Togami <[email protected]> wrote: On 12/18/2009 03:24 PM, Mark Martinec wrote: There is no error running pyzor directly or via spamassassin -D. It is only reporting an error during spamd startup. Perhaps spamd is running under a different uid that your command-line tests? Run tests under the same uid under which spamd will be running: su vscan -c 'spamassassin -D -t<0.msg' Mark Dec 18 15:49:55 localhost spamd[5096]: pyzor: opening pipe: /usr/bin/pyzor check < /tmp/.spamassassin5096Y9v0nmtmp Dec 18 15:49:55 localhost spamd[5097]: util: setuid: ruid=0 euid=0 Dec 18 15:49:55 localhost spamd[5096]: pyzor: [5097] finished: exit 1 Dec 18 15:49:55 localhost spamd[5096]: pyzor: got response: Traceback (most recent call last):\n File "/usr/bin/pyzor", line 8, in <module>\n pyzor.client.run()\n File "/usr/lib/python2.6/site-packages/pyzor /client.py", line 1022, in run\n ExecCall().run()\n File "/usr/lib/python2.6/site-packages/pyzor/client.py", line 180, in run\n os.mkdir(homedir)\nOSError: [Errno 13] Permission denied: '/root/.pyzor' Dec 18 15:49:55 localhost spamd[5096]: info: leaving helper-app run mode Dec 18 15:49:55 localhost spamd[5096]: pyzor: check failed: internal error, python traceback seen in response This is a pyzor + selinux bug, not spamassassin's fault. We have a go for spamassassin-3.3.0-rc1. Doing some further tests before cutting. Warren -- --j.
