Your message dated Wed, 1 Apr 2015 14:10:12 +0100
with message-id 
<CAB4XWXyRq6PZ_tBwFBJ9bC7q+FZp5YEroExe3thDB=qjrbn...@mail.gmail.com>
and subject line Re: transmission-daemon gets started at system startup though 
disabled in rcconf
has caused the Debian Bug report #761999,
regarding transmission-daemon gets started at system startup though disabled in 
rcconf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
761999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761999
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: transmission-daemon
Version: 2.84-0.1
Severity: important

Dear Maintainer,

I use transmission for some time now, via the web-gui to
transmission-daemon. Because I need special network configuration, I start transmission-daemon manually, and therefore have disabled it as a system service. Since a recent update, transmission-daemon appears to get started at startup anyway, though the rcconf settings have not been changed. This means that after each boot I have to first kill as root the already running
process, before I can start as user my specifically configured version.

My "/etc/transmission-daemon/settings.json", not attached, is actually empty.

Carsten


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages transmission-daemon depends on:
ii  adduser              3.113+nmu3
ii  init-system-helpers  1.21
ii  libc6                2.19-11
ii  libcurl3-gnutls      7.38.0-1
ii  libevent-2.0-5       2.0.21-stable-1.1
ii  libminiupnpc10       1.9.20140610-2
ii  libnatpmp1           20110808-3
ii  libssl1.0.0          1.0.1i-2
ii  libsystemd-daemon0   208-8
ii  lsb-base             4.1+Debian13
ii  transmission-common  2.84-0.1
ii  zlib1g               1:1.2.8.dfsg-1

Versions of packages transmission-daemon recommends:
ii  transmission-cli  2.84-0.1

transmission-daemon suggests no packages.

-- Configuration Files:
/etc/transmission-daemon/settings.json [Errno 13] Permission denied: u'/etc/transmission-daemon/settings.json'

-- no debconf information

--- End Message ---
--- Begin Message ---
Hello Carsten,

On Wed, Apr 1, 2015 at 2:07 PM, Carsten Allefeld
<[email protected]> wrote:
>> is this command returning any output:
>>
>> $ ls /etc/rc2.d/*transmission*
>
> Yes, /etc/rc2.d/K01transmission-daemon exists and points to
> /etc/init.d/transmission-daemon.

this is good, that means that when entering runlevel 2,
transmission-daemon is stopped (and it is not started automatically)

> To be honest, I'm not sure whether this bug persists. transmission-daemon
> does no longer start automatically on my system, but I'm not sure whether
> some later Debian update changed this, or at some point I made some hack
> that I've since forgotten about. Sorry, but its been a while.

indeed that confirms what said above, hence I am likely to consider
this bug as fixed and closing it.

Thanks for your report and checks,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

--- End Message ---

Reply via email to