Update default Samba log path
ClosedPublic

Authored by ngraham on Jun 2 2019, 9:01 PM.

Details

Summary

The current default path (var/log/samba.log) has not existed in years and is essentially
guaranteed to be wrong. Update the path according to the new location.

Diff Detail

Repository
R102 KInfoCenter
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
ngraham created this revision.Jun 2 2019, 9:01 PM
Restricted Application added a project: Plasma. · View Herald TranscriptJun 2 2019, 9:01 PM
Restricted Application added a subscriber: plasma-devel. · View Herald Transcript
ngraham requested review of this revision.Jun 2 2019, 9:01 PM
sitter accepted this revision.Jun 11 2019, 12:32 PM

https://github.com/samba-team/samba/blame/f33749fc84dacb164d1ac43f6bfcae7afcca34b3/packaging/Example/skeleton.tar looks to me like it has been that way for 21 years. I am inclined to think that the old path may have been some distro specific stuff.

That being said, the path can be configured at will, so ideally it should be read from the config. Which I think we could do since smb.conf looks to be an ini-style config. Something to think about maybe.

This revision is now accepted and ready to land.Jun 11 2019, 12:32 PM

https://github.com/samba-team/samba/blame/f33749fc84dacb164d1ac43f6bfcae7afcca34b3/packaging/Example/skeleton.tar looks to me like it has been that way for 21 years. I am inclined to think that the old path may have been some distro specific stuff.

That being said, the path can be configured at will, so ideally it should be read from the config. Which I think we could do since smb.conf looks to be an ini-style config. Something to think about maybe.

Yes, I had the same thought, but the key's value (/var/log/samba/log.%m) would require some parsing and munging which seems like it could be somewhat fragile.

This revision was automatically updated to reflect the committed changes.

True true. I was thinking with the static path as fall back anyway, just the "extra" loveliness of trying to follow the configured path as a first choice.