postgrey --daemonize --unix=/run/shm/postgrey.socket
--dbdir=/run/shm/postgrey
Works for me.
/T
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: postgrey
Version: 1.34-1.1
Followup-For: Bug #722136
root@spliff /var/log % postgrey --inet localhost:10023
2013/09/25-11:07:31 postgrey (type Net::Server::Multiplex) starting! pid(6677)
Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4
Binding to TCP port 10023 on host 127.0.0.1 with
Package: postgrey
Version: 1.34-1.1
Followup-For: Bug #722136
Hi,
Just letting you know that I had the same problem and the upstream
patch you suggested on the BTS fixed it.
- Craig
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Archi
Le dimanche 08 septembre 2013 à 11:19 +, Pascal Volk a écrit :
> On 09/08/2013 10:18 AM Pascal Volk wrote:
> > …
> > Insecure dependency in bind while running with -T switch at
> > /usr/lib/perl/5.18/IO/Socket.pm line 213.
> >
>
> I've applied the patch¹ from Yasuhiro Kimura. Now pos
On 09/08/2013 10:18 AM Pascal Volk wrote:
> …
> Insecure dependency in bind while running with -T switch at
> /usr/lib/perl/5.18/IO/Socket.pm line 213.
>
I've applied the patch¹ from Yasuhiro Kimura. Now postgrey starts again.
The comments in the patch seem plausible to me.
(Works for me
Package: postgrey
Version: 1.34-1.1
Severity: grave
Justification: renders package unusable
Hi Antonio,
today I've upgraded perl-base:amd64 5.14.2-21 -> 5.18.1-3. Since the upgrade
postgrey is unable to start. `service postgrey starts` returns 0. The only
thing I can find in the log file is:
6 matches
Mail list logo