First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 231220
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Net-Mail Packages <net-mail@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Kevin O'Gorman <kogorman@pacbell.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 231220 depends on: Show dependency tree
Show dependency graph
Bug 231220 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-07-08 20:22 0000
Fresh install of postgrey.  It installs a config file in /etc/conf.d, but
cannot
access it, so it uses entirely default config.

treat ~ # ls -l /etc/conf.d/postgrey
-rw-r----- 1 root postgrey 1915 2008-07-08 10:50 /etc/conf.d/postgrey

With that setup, it needs to be o+r, for mode 644.  Besides that, why is it
group postgrey?  The daemon executable is not SGID, and I expect it runs as
root:root, at least when it's reading its config.



Reproducible: Always

Actual Results:  
Daemon runs with default config and opens a TCP socket

Expected Results:  
Should open a UNIX socket, which is what I put in the config file.

------- Comment #1 From Jeremy Olexa 2008-07-08 23:01:00 0000 -------
*** Bug 231235 has been marked as a duplicate of this bug. ***

------- Comment #2 From Tobias Scherbaum 2008-07-21 17:53:41 0000 -------
(In reply to comment #0)
> Fresh install of postgrey.  It installs a config file in /etc/conf.d, but
> cannot
> access it, so it uses entirely default config.

Though it's group postgrey it should still be able to read the config. Anyway,
there was no reason to install this for root:postgrey (640), it was just using
the insopts set some lines above. This is fixed in CVS now (both 1.31 and
1.31-r2).

First Last Prev Next    No search results available      Search page      Enter new bug