https://bugzilla.novell.com/show_bug.cgi?id=785240
https://bugzilla.novell.com/show_bug.cgi?id=785240#c41
--- Comment #41 from Ákos Szőts 2012-11-28 23:53:27 UTC ---
1.) I haven't changed anything related to syslog to the default install. Zypper
says:
$> zypper se -i syslog:
i | rsyslog | The enhanced syslogd for Linux and Unix
i | syslog-service | Syslog service files & scripts
2.) I put the calls with $LOCKFILE into the restored SuSEfirewall2 but it
didn't find anything:
Nov 29 00:38:24 linux-suse SuSEfirewall2: Firewall rules set to CLOSE.
Nov 29 00:38:24 linux-suse SuSEfirewall2_init[840]: Loading basic firewall
rules LOCK BEGIN
Nov 29 00:38:24 linux-suse SuSEfirewall2_init[840]: ls: cannot access
/var/lock/SuSEfirewall2.pid: No such file or directory
Nov 29 00:38:24 linux-suse SuSEfirewall2_init[840]: cat:
/var/lock/SuSEfirewall2.pid: No such file or directory
I don't know whether is it normal or just indicates the previous that there is
two "LOCK BEGIN [...] LOCK END" calls with these time stamps:
Nov 29 00:38:24 linux-suse SuSEfirewall2_init[840]: Loading basic firewall
rules LOCK BEGIN
Nov 29 00:38:24 linux-suse SuSEfirewall2_init[840]: LOCK END
Nov 29 00:38:57 linux-suse SuSEfirewall2_setup[2941]: Loading firewall rules
LOCK BEGIN
Nov 29 00:38:57 linux-suse SuSEfirewall2_setup[2941]: LOCK END
Maybe I should put the debug lines before the error message line.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.