|Summary:||net-p2p/rtorrent-0.9.2 could not start initscript|
|Product:||Gentoo Linux||Reporter:||neko259 <neko259>|
|Component:||Current packages||Assignee:||Gentoo net-p2p team <net-p2p>|
|Package list:||Runtime testing required:||---|
Description neko259 2012-11-25 14:42:34 UTC
The daemon reports that it starts, but it's not actually started. When I try to start it as a normal user, I get screen messages: at first it asks me to give permission to /dev/pts3, then I have to create /var/run/screen and make it 777. Reproducible: Always Steps to Reproduce: /etc/init.d/rtorrentd start Actual Results: Nothing is started. Expected Results: rtorrent daemon is started. I'm using ~amd64 linux.
Comment 1 Jeroen Roovers (RETIRED) 2012-11-26 13:34:59 UTC
Maybe the init.d should be removed - it's a pretty horrible kludge anyway.
Comment 2 Alexander Vershilov (RETIRED) 2012-12-18 07:30:05 UTC
More info needed, as fresh install on a ~arch system works as needed. I.e. rtorrentd service really starts and report it status. It looks like screen + tmpfilesd problem.
Comment 3 Alexander Vershilov (RETIRED) 2012-12-26 07:00:39 UTC
(In reply to comment #0) > The daemon reports that it starts, but it's not actually started. When I try > to start it as a normal user, I get screen messages: at first it asks me to > give permission to /dev/pts3, then I have to create /var/run/screen and make > it 777. > > Reproducible: Always > This problem is related to old screen install, newer versions use $HOME to store sessions. Please upgrade your screen install to (>=app-misc/screen-4.0.3-r6) and report if you still have problems
Comment 4 Alexander Vershilov (RETIRED) 2012-12-29 14:14:37 UTC
(In reply to comment #1) > Maybe the init.d should be removed - it's a pretty horrible kludge anyway. Anyway init.d should not be removed as many resources (blogs and wiki) describes this solution. If you want I can make this init better, but it seems it's not very bad currently, at least it works.
Comment 5 Ben Kohler 2014-08-07 15:34:46 UTC
Closing this bug as all non-working screen versions have been gone a while. Please do re-open if this issue persists with current screen versions.