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
co
severity 385137 normal
thanks
> 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
I beg to disagree. This bug belongs to the "normal" category
according to definitions given in the Debian BTS.
The "Using Samba" documents are also provided by the samba-doc package,
which package description states that it contains "all the documentation
that comes in the original tarball". I find it strange that the
documentation in the original tarball is incorrect, but what I find the
strangest is t
Am Dienstag, 29. August 2006 13:12 schrieb N VZ:
> 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.
Note that "Using Samba" is not the official documentation for Samba. It is
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 ta
5 matches
Mail list logo
