Bug 12777 - samba triggers HDD each time a client is connected because of msg.sock creation.
Summary: samba triggers HDD each time a client is connected because of msg.sock creation.
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: All Linux
: P5 normal (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-07 09:35 UTC by Alexander Golubev
Modified: 2023-01-13 01:22 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Golubev 2017-05-07 09:35:12 UTC
Samba triggers HDD each time a client is connected. This happens only because each such moment a socket is created under "msg.sock" dir, which is located under private dir (which obviously should be located on a persistent media).

There were a few messages about this on mail list (see [1] and bellow the thread).

Also it doesn't corresponds FHS well according which such stuff as sockets should go to [/var]/run/.

I would like to ask that those files would be moved away to [/var]/run/samba or whatever place which is meant for temporary runtime files (and mounted to tmpfs by most distros).

[1] https://lists.samba.org/archive/samba/2016-March/198256.html