Re: Avoiding to mount /run/lock
On Fri, 4 Mar 2016, Sven Hartge wrote:
Sven has a point: perhaps increasing the size or finding out what's up
with samba. That said, if you are using sysvinit, the script responsible
for mounting /run/lock is /etc/init.d/mountkernfs.sh; if you're on
systemd I'm out of my depth, sorry.
Yes its systemd now...
I see reports from Samba users dating back quite a while about big
locking.tdb files in /run/lock or /var/lock, for example
The biggest file is a file called unexpected.tdb.
Samba documentation says it a file for "Unexpected packet queue needed to support windows clients that respond on a different port that the originating reques."
The Sernet guys, whor provided the Samba 4 packages back then changed
the location for the locking.tdb to /var/cache/samba to avoid that
Maybe Debian should to the same?
Looking at smb.conf, you can also do this, just change "lock directory"
to a sane value. The default is "lock directory = /var/run/samba".
Sounds like a reasonable workaround. What would be a proper path? /var/lib/samba?
Still I guess its not really an option to not know where those tempdirs can really be configured.