It does have a major effect on usability because the user cannot log in a useful way.
This was brought to my attention when a user on freenode needed to log
for each share instead of each client and I asked why. Reason being in
this case was to simplify logs so that reguardless of what users may
come and go or what ips they may get on the network there will just be
a log for each service offered. Logging for each client can generate a
huge collection of log files that will go stale. If user 10.0.0.105 is
no longer on my network I will still have logs for him until I clean
them up. But if I log each service instead of each user I will always
have the same number of log files regaurdless and the old users will be
phased out of the logs by a simple rotation.
In any case the real bug seems to be in Oreilly's documentation and I
suggest the best course of action would probably be to pull the
document from debian as it is misleading and incorrect, or to send a
patch on the document to fix the errors found according to the rules of
the GFDL. Then file this seemingly useful logging feature as a wishlist
bug. I overlooked the fact that the document was not official
documentation as it was on the official site and being distributed in
debian with the official documentation.
I apologize for the ignorance but my point stands that this doesnt work
and it really seems like it should. Flexible logging options are a good
thing and I am not the only one who things so. Oreilly dreamed up this
sort of functunality when they wrote that document. Francis Strickland
who posted on lists.samba.org in January, and the user I spoke to
yesturday wanted to do it as well.
