Summary: | app-misc/screen unable to use /var/run/screen/ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | satmd <satmd> |
Component: | New packages | Assignee: | Sven Wegener <swegener> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | eras, kensington, shell-tools |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
satmd
2012-01-13 15:04:40 UTC
See bugs #333821 #381451 #381451. They are all more or less the same problem. Bug 370453 suggests /var/lib too #384053 is the bug regarding syslog-ng, where I solved it locally by changing the path to /var/run/syslog-ng and changing its permissions accordingly, that was prior to openrc using tmpfs /run. Right now I'm forced to have USE="-caps" for syslog-ng, it seems. Summary: syslog-ng with USE=+caps relies on this bug too (In reply to comment #2) > Bug 370453 suggests /var/lib too Bleh. That's an ugly hack. My vote would be to have an init script to create the run dir so that one can run the init script at boot if necessary. Or just get rid of multiuser flag and have the socket under $HOME. (In reply to comment #4) > (In reply to comment #2) > > Bug 370453 suggests /var/lib too > > Bleh. That's an ugly hack. My vote would be to have an init script to create > the run dir so that one can run the init script at boot if necessary. > > Or just get rid of multiuser flag and have the socket under $HOME. Huh? This bug is simply triggered by running 'screen' itself. There is no init script requirement. Ugh, screen can't run because screen can't create a socket (unless it is suid) because the parent dir for the socket does not exist or has limited permissions because, for example, /var/run is on tmpfs. One way of making sure that the parent dir with correct permissions exists is through an init script. That is definately more complicated than just changing the socket dir to a non tmpfs location (also needed for systemd, I guess) *** This bug has been marked as a duplicate of bug 333821 *** |