Re: How to duplicate a copy of all incoming and outgoing mail
Patrick Dung wrote: It is system wide, not specific user (~/.forward) Is it possble with Sendmail? How about Postfix and Qmail? qmail: qmailtap http://www.inter7.com/?page=qmailtap Other than that, see also maildrop (same people) or fetchmail. Google that or try the ports tree. Billy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.d ppp dependency
[EMAIL PROTECTED] wrote: Hi when using ppp together with pf there seems to exist a dependency problem. I start ppp and pf with : ppp_enable=YES and pf_enable=YES in rc.conf. At startup when the pf rulefile is loaded, the tun0 (which I use in the pf config) device does not yet exist and therefore the rules can not load. I noticed that in /etc/rc.d/ppp-user, ipfilter is resynced after ppp has started. Shouldn't the same be done for pf? thanks Stefan P.S. a similar problem exists with sshd when a ListenAddress directive is used with an address configured to tun0 Attn: I have been trying to get the same exact problem dealt with for ipnat and renaming interfaces. It appears that under FreeBSD 5-Stable, that although we are welcome to rename a network interface (like fxp0) to whatever we want (say out0), there seems to be a problem with the order in which things happen at boot. RENAMING happens after the ipnat has started, and so I feel that we need to re-sync ipnat after the renaming occurs. Otherwise, ipnat seems to have the old interface names, and ipnat will not work. Notice that in the rcorder of things, we see this (I skipped a bunch for brevity): ipfilter ... ipmon ... ipnat ipfs ... netif (interface renaming occurs; resync of ipfilter) isdnd ppp-user ipfw dhclient nsswitch ip6addrctl atm2 routing ip6fw network_ipv6 mroute6d route6d mrouted routed NETWORKING ... pflog pf pppoed ... localpkg natd What I see is that we need an IF-THEN-ELSE statement in the rcorder system someplace, that can notify pf if ppp is being used, and that will force ipnat to reload, etc. The ppp-user file, as you say, might need to reload pf if necessary. A simple patch could be thought up and attached here, huh? Can you post some of these comments as a bug (PR) to the FreeBSD system? I have one that could probably be fixed if my patch is used. See my related PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/81606 You might refer to PR 81606 as potentially being a similar issue with rcng. These thigns are slowly coming to light. rcng has got a lot of little tweaks it needs, especially if we start to let ports interact with the system rcng files. Billy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Cold Reboot (or cold restart) FreeBSD? locore.s hack attempt
I want to do a cold reboot of FreeBSD due to (what seens to be) a problem with the FreeBSD 5.3 system on my particular machine. To make a long story short, I have determined that FreeBSD 5.3 sputters and coughs when it tries to reboot this system. (The problem wasn't on 4.7, for example, and DOS can reboot the machine fine.) I believe the solution (barring a change of the kernel I'm not sure how to do) is to merely rewrite the code which send the command to reboot the system. I want to be able to do a shutdown -r now, or merely a reboot from single user mode, etc. and the system restart, do its full POST, count memory, and run properly. So here's my unified diff, which did not seem to work: -Code --- locore.sThu Jul 8 17:35:34 2004 +++ /usr/src/sys/i386/i386/locore.s Wed Feb 2 01:50:36 2005 @@ -214,7 +214,8 @@ movsb #else /* IBM-PC */ /* Tell the bios to warmboot next time */ - movw$0x1234,0x472 +/* movw$0x1234,0x472 */ +movw$0x,0x472 /* Billy: Perform Cold Reboot! */ #endif /* PC98 */ /* Set up a real frame in case the double return in newboot is executed. */ -Code Recompiling my kernel and using that diff did not work. The system would still lock up and freeze when I attempted to do a shutdown -r now. The 0x472h address is supposed to point to a region of memory that the BIOS looks at when deciding to do a cold or warm restart. Perhaps doing this in locore.s is not working somehow, or that region of memory gets corrupted. So to see the full discussion of my problem in detail, see the archives of the freebsd-questions list: http://lists.freebsd.org/pipermail/freebsd-questions/2005-January/074567.html (my original post) Here's what I came up with: http://lists.freebsd.org/pipermail/freebsd-questions/2005-February/074728.html Well, so far I tried this hack: http://lists.freebsd.org/pipermail/freebsd-questions/2005-February/074867.html This problem is very weird, because only FreeBSD 5.3 seems to break the rebooting ability of this machine. The underlying problem might have to do with some sort of aggressive use of the BIOS memroy region or some reserved memory which causes a warm (or perhaps even the cold) reboot to fail. IF that's the case, is there a hack to reserve memory from FreeBSD's kernel so that these secret regions get left in tact? Other than that, would someone like to see if my hack of locore.s Works For Them? I'm curious to see if someone else's computer will perform the cold restart (count memory). This code region is apparently about 10 years old or more (pre-3.0.5), so it would be interesting to hack it now. As a side note, I believe that linux and others allow you to decide on which reboot flavor you prefer. Thanks, Billy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
