On an unrelated note, pound would not start at first because it was
looking in the wrong place for the configuration file. Why does the
installation routine put that file in one place while the binary
executable looks in another? Is that happening because of something
I've done?
[root@poundvm1 ~]# pound -v
starting...
Control "/var/lib/pound/pound.cfg" bind: No such file or directory
[root@poundvm1 ~]# mkdir /var/lib/pound
[root@poundvm1 ~]# ln -s /usr/local/etc/pound.cfg /var/lib/pound/pound.cfg
[root@poundvm1 ~]# pound -v
starting...
[root@poundvm1 ~]# ps -ef | grep pound
pound 2284 1 0 11:25 ? 00:00:00 pound -v
pound 2285 2284 0 11:25 ? 00:00:00 pound -v
I think that's a function of the 'configure' line you used. I don't
have that problem on my system.
Regards,
--
Dave Steinberg
http://www.geekisp.com/
http://www.steinbergcomputing.com/
http://www.redterror.net/
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
