Replying to my own post just to say I fixed it for the benefit of anyone
else that may run into this issue.
Thanks to those that replied.
The problem was that the initrd contained the persistent-net-rules from
the host system.
Trouble only occured when the the disk generation and the boot were do
Hi all,
I have a machine running debian etch (2.6.18) with an onboard (8159)
ethernet interface and a firewire port.
By default both the kernel (as witnessed by dmesg) and /sys/class/net see
eth0 = firewire
eth1 = ethernet
If I blacklist the ieee1394, uhci1394 and eth1394 modules (or
disactivate
Hi all,
I am looking for a way to find any files on my system in certain
directories (such as /usr/lib, ...) that have NOT been installed by a
package.
I know about debsums but that only tells me if packaged files have been
modified.
I probably could write a script to do it something like th
Thank you for reply.
I have indeed set up SASL authentication as you describe and the actual
authentication (which occurs at each connection to the remote SMTP
server) works fine.
The problems are :
1) My ISP doesn't like *empty* AUTH=<> in the "MAIL FROM:" field of
the envelope. They *do*
Hi,
I have been succesfully running postfix on Sarge as a local mailserver
relaying all outbound mail (from multiple internal accounts) to my ISP.
However my ISP has just decided to require SMTP authentication.
I have set up SASL following the postfix documentation and the
authentication pha
since it is started at level S12 wheras hotplug is S40.
All works after a manual start.
Is this a bug? (and if so in apcupsd or hotplug?)
Should I change the start up levels so that apcupsd comes after hotplug?
Any other ideas?
Thanks,
Martin Fuzzey
--
To UNSUBSCRIBE, email to [EMAIL
6 matches
Mail list logo