[tahoe-lafs-trac-stream] [tahoe-lafs] #961: init scripts included in the Ubuntu apt-get install for tahoe-lafs

[tahoe-lafs]

#961: init scripts included in the Ubuntu apt-get install for tahoe-lafs
-----------------------------+--------------------------------
     Reporter:  stott        |      Owner:  zooko
         Type:  enhancement  |     Status:  reopened
     Priority:  minor        |  Milestone:  1.7.1
    Component:  packaging    |    Version:  1.5.0
   Resolution:               |   Keywords:  init security docs
Launchpad Bug:               |
-----------------------------+--------------------------------
Changes (by zooko):

 * status:  closed => reopened
 * resolution:  fixed =>


Old description:

> /etc/init scripts should be included by default to start tahoe-lafs if
> there are configured nodes, introducrs or helpers, Tahoe should auto-
> start.  Run level 3, after most other services are up and running.

New description:

 /etc/init scripts should be included by default to start tahoe-lafs if
 there are configured nodes, introducrs or helpers, Tahoe should auto-
 start.  Run level 3, after most other services are up and running.

--

Comment:

 I was talking with intrigeri about including Tahoe-LAFS in Tails
 (https://tails.boum.org/), and he pointed out this Debian bug report:
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652003 . That bug report
 by Thomas Pierson <contact at thomaspierson.fr> says that he can't find the
 actual init script anywhere. Sure enough, reviewing this ticket it appears
 to me that we accidentally omitted the actual init script (final version
 attached to this ticket by ioerror: attachment:debian-init-script-patch-
 final).

 Daira: did you review attachment:debian-init-script-patch-final? You wrote
 review notes in comment:22.

 ioerror: why did you post the diff in comment:14? Why remove the PID file
 variable setting?

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/961#comment:25>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage