Re: Procmail site-wide recipe's
This still requires a .forward in each home directory to pipe the mail through procmail. On Tuesday, February 11, 2003, at 11:01 AM, JacobRhoden wrote: On Tuesday 11 February 2003 10:52, BSD Freak wrote: I am running a 4.7-R/sendmail mail server. I currently use procmail on a few email accounts using a .forward in each home directory. Does anyone know how I can make a procmail recipe apply to all users on the mail server? I had no idea until I typed 'man procmail' and read the first two paragraphs (: Have fun. - jacob Jacob RhodenPhone: +61 3 8344 6102 ITS DivisionEmail: [EMAIL PROTECTED] Melbourne University Mobile: +61 403 788 386 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: BSD on Tecra 8100 w/Docking Station
I hate to be a party pooper but I think you'll find that if Linux
(which supports a larger range of hardware than FreeBSD) doesn't
support your card then FreeBSD probably won't. In any case consult the
freebsd hardware notes. Your best bet is just to buy a cheopo PCMCIA
NIC...
-Allan.
On Sunday, February 9, 2003, at 09:50 PM, Colin J. Raven wrote:
Greetings everyone!!
I'd very much like to install FreeBSD on the above laptop. However,
there is a problem in that it sits full time on a Toshiba Docking
Station...in which sits the NIC. Although ('natch) there are PCMCIA
slots, I've never bought a card, owing to the existence of the dock. I
concede that may have been a mistake in hindsight, but now I have to
(try and) work with what I've got.
W2K recognizes the docking station NIC with nary a murmur and always
has. BUT since buying this machine I have *never* got any Linux install
to recognize the dock network card. I'm determined to install *a* 'nix
on this machine, yet this seems to be *the* stumbling block no matter
what. I've tried FreeBSD on a friend's machine and believe I just may
be
hooked! :-)
I went on an orgy of reading to see if anyone solved this. To date I've
read a whole lot of; try this, it might work (it didn't in every
case!) and despite many weeks of trolling around I'm as stumped as when
I began.
Can anyone offer a definitive answer to this - *the* most important
question of all?? I'd truly appreciate a solution to the
issue.somewhere, somehow.
Regards TIA,
-Colin
--
Colin J. Raven
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Monitoring the entire filesystem?
I use /usr/ports/security/tripwire-131 Works great... -Allan On Monday, February 10, 2003, at 06:44 AM, Kevin Fogleman wrote: Is there an existing way to monitor the entire filesystem for changes to any file, particularly changes in extended attributes? I've read over the documentation for kqueue, but some things were left unclear. For example, it appears the man page has not been updated for 5.0 and thus doesn't specify whether or how extended attributes can be monitored for modifications. Also, it appears that kqueue needs a file descriptor for each file that one would want to monitor, making any large-scale file monitoring impractical. Is there any other way in FreeBSD to be notified of file modifications in a way that would allow one to monitor the whole file system or large portions of it? I don't really need to know whether a particular attribute changed, but rather just whether any of them changed. --Kevin Fogleman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
