Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: qpopper vs. tcpd
- To: tlug@example.com
- Subject: Re: tlug: qpopper vs. tcpd
- From: Dave Gutteridge <dave@example.com>
- Date: Fri, 27 Nov 1998 20:15:49
- Content-Type: text/plain; charset="us-ascii"
- In-Reply-To: <13918.31472.216457.326499@example.com>
- References: <3.0.6.32.19981127182032.005adb40@example.com><3.0.6.32.19981127162212.0058a100@example.com><3.0.6.32.19981127145738.0057db20@example.com><3.0.6.32.19981127140543.009af100@example.com><3.0.6.32.19981127125607.00573610@example.com><Pine.LNX.3.96LJ1.1b7.981127101400.24851S-100000@example.com .jp><199811260012.JAA01985@example.com><3.0.6.32.19981127182032.005adb40@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>Now if you use "cat >file" instead, it won't echo to your screen; >instead it will echo to "file". Go ahead, try it; then type "cat >file" to see what's in "file". The shell, which normally handles both >key input and screen output, has redirected screen output away from >the screen and into "file". And "cat <file1 >file2" has the same >effect as "cp file1 file2". You knew all that, right? Er... yeah... of course... Actually, what i knew was that i could type "cat file" and get the contents of file, just in the same way that "more file". Now that i think about it, what is the difference between saying "cat file > file2" and "more file > file2". Isn't it the same result? >Why do this? Well, actually, before handing off the internet >connection to qpopper or whatever, it can check the source address and >some other stuff (lots of stuff, actually) and deny access. (Just >like the shell can set environment variables, search the path for >prog, etc.) So if you know that you're only going to use POP3 from a >few IP addresses, or some specific domain, you can use tcpd to enforce >those restrictions for you. That sounds pretty darned neat. I like the idea of forcing restrictions - makes me feel in charge. But - despite all the new information for which i am very grateful to have - part of my original question remains unanswered. Based on what Yan said, i now know that ipop is doing my POP services. That's cool and all, but let's assume - because it's a good assumption - that i still want to make it qpopper instead. Do i need to remove ipop before installing qpopper? Or will qpopper take over port 110 and nudge ipop out of the way for me? I'm kind of worried that the two will vie for attention on the same port and cause trouble. ________________________________ Dave Gutteridge 3D Computer Animation Specialist e-mail: dave@example.com http://www.d-rave.com ________________________________ ---------------------------------------------------------------- Next Technical Meeting: 12 December, 12:30 HSBC Securities Office Next Nomikai: 15 January 1999, 19:30 Tengu TokyoEkiMae 03-3275-3691 ---------------------------------------------------------------- more info: http://tlug.linux.or.jp Sponsors: PHT, HSBC Securities
- Follow-Ups:
- Re: tlug: qpopper vs. tcpd
- From: "Stephen J. Turnbull" <turnbull@example.com>
- References:
- tlug: qpopper vs. tcpd
- From: Dave Gutteridge <dave@example.com>
- Re: tlug: Apache restart
- From: Dave Gutteridge <dave@example.com>
- Re: tlug: Apache restart
- From: Dave Gutteridge <dave@example.com>
- Re: tlug: Apache restart
- From: Darren Cook <darren@example.com>
- tlug: Apache restart
- From: Dave Gutteridge <dave@example.com>
- tlug: Noseguy
- From: Frank Bennett <bennett@example.com>
- tlug: qpopper vs. tcpd
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: tlug: qpopper vs. tcpd
- Next by Date: RE: tlug: qpopper vs. tcpd
- Prev by thread: tlug: qpopper vs. tcpd
- Next by thread: Re: tlug: qpopper vs. tcpd
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links