Bug 358635 – net-p2p/transmission-2.21: potential init script problem with --background vs rc_start_wait > 0

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Leho Kraav (:macmaN @lkraav) 2011-03-13 00:17:05 UTC]

$ qlist -IUv baselayout openrc
net-p2p/transmission-2.21 (libnotify)
sys-apps/baselayout-2.0.1-r1
sys-apps/openrc-0.7.0 (elibc_glibc kernel_linux ncurses pam unicode)

i enabled in rc.conf today a 3000ms delay for services, to slow the boot down so i can monitor it better:

rc_start_wait=3000

my default runlevel has about 40 entries. this caused a problem only with transmission, causing a "received an interrupt" error immediately after start-stop-daemon --start command.

let it be noted that before, with #rc_start_wait=0, transmission init script worked as expected.

transmission-daemon actually does start up (verified with ps), but start-stop-daemon has trouble detecting it and init script fails.

since /usr/bin/transmission-daemon detaches just fine on its own, i could not understand why ebuild uses --background. removing this switch immediately fixed the problem and did not produce any apparent side effects.

i therefore propose removing --background from the init script. anyone able to test this with baselayout-1?

Reproducible: Always

[Comment 1 Peter Volkov (RETIRED) 2011-03-22 15:03:02 UTC]

Thank you for report, Leho. Previously transmission-daemon did not have ability to go background and this switch is left from that days. I'll drop --background with next version/revision bump.

[Comment 2 Peter Volkov (RETIRED) 2011-04-06 16:26:54 UTC]

Thank you again. Fixed in transmission-2.30_beta1.