https://bugzilla.novell.com/show_bug.cgi?id=785240
https://bugzilla.novell.com/show_bug.cgi?id=785240#c40
--- Comment #40 from Ludwig Nussel 2012-11-27 11:01:19 CET ---
Ok, now it gets interesting. There are two things going wrong
1. the logger call shouldn't take ages
2. SuSEfirewall2 shouldn't even get there
1. might be a systemd/journald bug. Maybe the syslog implementation takes time
to start up? Which systlog do you use?
2. SuSEfirweall2_init is supposed to run once and as first instance of
SuSEfirewall2. The lock file is /var/lock/SuSEfirewall2.pid so on tmpfs. It
cannot exist at SuSEfirewall2_init time unless some other process that runs in
parallel executed SuSEfirewall2.
So to debug 2) further you may restore SuSEfirewall2 to it's original state and
e.g. add an ls -l $LOCKFILE or cat $LOCKFILE to the start of setlock(). If a
lock file shows up there you may add some "ps faux" call or something like that
to see what's running in parallel there.
--
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.