PortAssist Manager appears to use port 8080 by default for it’s web interface. On my server, that’s the port that Squid uses! It caused a few headaches until I worked out PAM was binding to the port before ‘squid’ had a chance to bind to it (and therefore squid aborted).
Anyway, I reconfigured PAM to use port 8000, which was fine, but I rebooted the machine today and PAM had started using port 8080 again, which caused the same problem as before with people trying to use the squid proxy meant to be running on port 8080 getting the PAM login page instead.
I’ve reconfigured PAM again to use port 8000. I’ve checked the /var/local/pam/vq/server/server.cfg file and it definitely shows port 8000:
What would cause this to be over-ridden (or simply ignored) at startup time? Is there anywhere else that the port number can be specified by anything run from the ‘digipams’ script installed in /etc/init.d?