Michael Mansour wrote:
For this (on a 5.2 i386 box), I have:
options bond0 mode=1 miimon=100 use_carrier=1
and it's never failed.
Thanks Michael, it could be x86_64 specific maybe...
JM
--
Jean-michel BARBET
On Tue, 31 Mar 2009, Jean-Michel Barbet wrote:
Michael Mansour wrote:
For this (on a 5.2 i386 box), I have:
options bond0 mode=1 miimon=100 use_carrier=1
and it's never failed.
Thanks Michael, it could be x86_64 specific maybe...
Or it could be pure statistics. It also depends on usage.
Troy Dawson wrote:
And the dbus update required an updated selinux-policy for SL 50, 51 and
52.
We apologize for any problems this oversight might have caused.
It appears that the new selinux-policy will not allow spamc to be run
by procmail. This effectively disables spamassassin. Is
I have had system freezes, but am not running a server or
bonding. It is a sl5.2 x86_64 system. I noticed that acroread
was running, though it should not have been and was using
ever increasing cpu percentage as the system proceeded to freeze. I've
made a soft link to evince from where acroread
John Franks writes:
It appears that the new selinux-policy will not allow spamc to be run
by procmail. This effectively disables spamassassin. Is there any
way to fix this? I am being inundated by spam. This is SL 51 (x86_64).
This is in bugs:
On Tue, 2009-03-31 at 10:26 -0400, W. J. Kossler wrote:
I have had system freezes, but am not running a server or
bonding. It is a sl5.2 x86_64 system. I noticed that acroread
was running, though it should not have been and was using
ever increasing cpu percentage as the system proceeded to
On Tue, 31 Mar 2009, W. J. Kossler wrote:
I have had system freezes, but am not running a server or
bonding. It is a sl5.2 x86_64 system. I noticed that acroread
was running, though it should not have been and was using
ever increasing cpu percentage as the system proceeded to freeze. I've
On Tue, 31 Mar 2009, Craig Moore wrote:
On Tue, 2009-03-31 at 10:26 -0400, W. J. Kossler wrote:
I have had system freezes, but am not running a server or
bonding. It is a sl5.2 x86_64 system. I noticed that acroread
was running, though it should not have been and was using
ever increasing cpu
