home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.misc
- Path: sparky!uunet!gumby!yale!cs.yale.edu!not-for-mail
- From: anselmo-ed@cs.yale.edu (Ed Anselmo)
- Subject: Re: Popd and Popper problem.
- In-Reply-To: horgan@mantis.csu.murdoch.edu.au's message of 20 Jul 92 04: 50:14 GMT
- Message-ID: <14pmjpINNqp6@BIGBIRD.CF.CS.YALE.EDU>
- Lines: 18
- Sender: news@cs.yale.edu (Usenet News)
- Nntp-Posting-Host: bigbird.cf.cs.yale.edu
- Organization: Yale University, Dept. of Computer Science, New Haven, CT
- References: <horgan.711607814@mantis>
- Date: Fri, 24 Jul 1992 19:44:57 GMT
-
- Both popd and popper are probably doing the equivalent of
- getservbyname("pop", proto), so both are trying to bind port 110.
-
- I run the popd from the MH 6.7 distribution on a few machines here and
- do both pop2 and pop3 by explicitly specifying a port number on
- startup. I haven't used popper or the LifeLine mail popd so I don't
- know if this is an option.
-
- /etc/rc.yale: /usr/local/etc/popd -p 110 2> /dev/null &
- /etc/rc.yale: /usr/local/etc/popd 2> /dev/null &
-
- My /etc/services file is the other way around -:)
-
- pop 109/tcp # Post Office
- pop3 110/tcp # Post Office
-
- --
- Ed Anselmo anselmo-ed@cs.yale.edu {harvard,cmcl2}!yale!anselmo-ed
-