Comment 3 for bug 1252441

Marius Gedminas (mgedmin) wrote :

Given that I use postgrey on my servers, and that I will upgrade to 14.04 LTS when it comes out, I decided to try some preventative maintenance and see if postgrey is really broken on 13.10.

I was unable to reproduce your problem:

    $ sudo apt-get install postgrey

    $ ps $(cat /var/run/postgrey.pid)
      PID TTY STAT TIME COMMAND
    17720 ? Ss 0:00 /usr/sbin/postgrey --pidfile=/var/run/postgrey.pid --daemonize --inet=10023

    $ sudo lsof -i TCP:10023
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    /usr/sbin 17720 postgrey 6u IPv4 2248799 0t0 TCP localhost:10023 (LISTEN)

    $ less /var/log/syslog
    Nov 19 09:56:41 platonas postgrey[17720]: Process Backgrounded
    Nov 19 09:56:41 platonas postgrey[17720]: 2013/11/19-09:56:41 postgrey (type Net::Server::Multiplex) starting! pid(17720)
    Nov 19 09:56:41 platonas postgrey[17720]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4
    Nov 19 09:56:41 platonas postgrey[17720]: Binding to TCP port 10023 on host 127.0.0.1 with IPv4
    Nov 19 09:56:41 platonas postgrey[17720]: Setting gid to "139 139"
    Nov 19 09:56:41 platonas postgrey[17720]: Setting uid to "127"
    Nov 19 09:59:45 platonas postgrey[17720]: 2013/11/19-09:59:45 Server closing!

Hm.