Normal log is done per host. We have client with name foo then login is into directory: /var/log/log.foo But /var/log/log.smbd and /var/log/log.smbmount is samba's system logs. If someone tryes to rename pc to smbmount or smbd :(( I sugested to do system log: /var/log/smbd.log /var/log/smbmount.log I didn't konw how works samba when two loging file has the same name.
yeah mandrake has a patch for this, i think. good idea. will fix in the near future.
Okay I'm actually not really sure what you're talking about, could you please clarify, what, if anything, we need to do? See this: http://us1.samba.org/samba/whatsnew/macroexploit.html Now, our example smb.conf file has the correct way to do the per machine logging, as per the above article with regards to syntax. Also, it was Redhat that has a small patch for SAMBA logging code, but it doesnt quite do what I originally thought it did. Please take a look at their patch and lemme know what you think. Also, would --logfilebase come into play for this at all? I'm not sure if there's anything to fix here at the moment.
## samba-2.2.7a I only want to say that deamon/command nmbd,smbd,smbmount do loging into: /var/log/samba/log.<name> eternal pc cnnections is loging into: /var/log/samba/log.<name> what hapens if someone has pc with name nmbd or smbd or smbmount?
i dont think i can fix this, man. you should really ask the samba folks about this i suppose.
afaik this isnt an issue, logging is not changed by our ebuild.
