Description of problem: PrivateTmp setting in httpd.service unit file breaks zoneminder and rtorrent. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
CC: (none) => anssi.hannula
CC: (none) => mageia
Blocks: (none) => 2120
Hi Barry, can you clarify how this breaks zoneminder and rtorrent? In other words, what error messages etc. do you get? How would one test this?
@remmy: I actually asked Dave to open this :) The basic problem is that both rtorrent and zoneminder run as independent apps, but drop a unix socket into $TMP for IPC purposed. Web applications are then configured under apache that talk to these sockets. If apache has it's own /tmp, it simply can't see them and the IPC system is broken. Mechanisms to work around would be using abstract unix sockets (rather than socket files) or using network sockets for IPC, but I think the immediate short term fix is to simply drop PrivateTmp for now and revisit it when we have a bit more breathing space.
rtorrent can IIRC be configured to use either a network socket or a unix socket, but I guess many people do configure it to use some /tmp/foobar socket. In addition, rutorrent (a php gui for rtorrent) explicitely commands rtorrent to write/read to some files under /tmp, which is broken even if rtorrent communication uses a network socket (I'm not sure why it does that, though, AFAICS it could just use the rtorrent "execute.capture" RPC command...). I agree to drop PrivateTmp at least for mga2.
CC: (none) => remco
Status: NEW => ASSIGNEDCC: (none) => guillomovitchAssignee: bugsquad => guillomovitch
Just fixed in -7mga.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED