Your message dated Wed, 30 Aug 2006 14:21:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385137: Processed: severity of 385137 is wishlist
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: samba
Version: 3.0.22-1
Severity: important
[global]
log file = /var/log/samba/%S.log
as described in Chapter 12 of the Using Samba guide to log for each
service (share) simply creates /var/log/samba/%S.log litterally and
doesnt parse it as a variable.
It is also stated in Chapter 6 table 6-8 pf the Using Samba guide that the log file string "Works with all variables."
which is directly inconsistant with Gerald Carter's reply to the post
Francis Strickland had made about this issue back in january on
lists.samba.org @
http://lists.samba.org/archive/samba/2006-January/115979.html
its outlined in the Using Samba document both on samba.org and in the
samba-doc package in debian that this is suppose to work for creating
seperate logs for each share instead of for each client machine. This
should be considered a serious bug, but I have filed it as important
because it doesnt affect usability for all users. However the bug makes
the documentation invalid and for this reason it is every bit serious.
--- End Message ---
--- Begin Message ---
tags 385137 wontfix
On Wed, Aug 30, 2006 at 02:40:35PM +0200, Øyvind Malagmyr Hvidsten wrote:
> In a network like mine, the user changes more often than the service,
No, it doesn't. The user changes, and *then* the service changes; every
time a different user connects, they have to re-connect to the service.
That's AIUI one reason why logging by service is such a problem, because
there's a whole load of information that might need to be logged that isn't
tied to a service, leaving you with nowhere to log this information but the
default log.
Anyway, I suspected this was upstream's answer; now that it's confirmed,
I'll close this bug as a 'wontfix'.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
