http://bugzilla.novell.com/show_bug.cgi?id=606972
http://bugzilla.novell.com/show_bug.cgi?id=606972#c2
Marc Chamberlin changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
--- Comment #2 from Marc Chamberlin 2010-05-20 15:45:11 UTC ---
Uh Werner Did you NOT read my suggestion? If the syslog daemon is broken into
two parts, or redesigned so as to accommodate dynamic logging to available
resources, one for local filesytem and one for remote, then the logging of what
the the network daemon does, can be done initially to the local filesystem and
later to a remote filesystem when it becomes available, if and only if the user
has really specified remote logging. If this is done right, then even the local
filesystem log could be transferred/copied to the remote filesystem, if indeed
that is where logging is configured to be done...
I strongly suspect MOST users will NOT be doing logging to a remote file system
so you have in effect the tail wagging the dog or the cart before the horse as
they say! And it is extremely important to be able to understand what happened
in network initialization if something failed.
Consider this an enhancement request if you like, but it really should be fixed
and I take strong exception to your decision.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
