4 Mar
2001
4 Mar
'01
22:38
Yes I've got the same messages about SuSEfirewall failure. I just wonder if it's due to SuSE changed run levels (5 instead of 3) and they just forgot to reconfigure SuSEfirewall initializing scripts. May somebody from SuSE gives us clarification on this issue. By the way is this a bug or a feature putting .kde2 and .kde in / directory? Thanks Alex On Sunday 04 March 2001 14:14, Matthew Johnson wrote:
Reloaded my server last night, apart from warning during stage 2 of the firewall start it then came up as failed on all the 3, but seems to working. Is that normal?
Matt
-- MS Windows users should be covered under the Americans with Disabilities Act