tahoe-lafs/trac-2024-07-25

support running as a service on Windows #1283

New issue

Open

opened 2010-12-26 05:54:36 +00:00 by davidsarah · 2 comments

davidsarah commented

2010-12-26 05:54:36 +00:00

Owner

The Windows GUI app (removed by #1282) supported running a Tahoe node as a service. Currently, tahoe start does the same thing as tahoe run on Windows, but it would be better for it to run a service. source:src/allmydata/windows/tahoesvc.py has some of the code needed, although it currently depends on the Tahoe process being an executable file created by py2exe.

This should be implemented in a way that does not preclude running more than one node with different base directories.

The Windows GUI app (removed by #1282) supported running a Tahoe node as a service. Currently, `tahoe start` does the same thing as `tahoe run` on Windows, but it would be better for it to run a service. source:src/allmydata/windows/tahoesvc.py has some of the code needed, although it currently depends on the Tahoe process being an executable file created by `py2exe`. This should be implemented in a way that does not preclude running more than one node with different base directories.

tahoe-lafs added the

labels 2010-12-26 05:54:36 +00:00

tahoe-lafs added this to the undecided milestone 2010-12-26 05:54:36 +00:00

davidsarah commented

2011-01-16 19:24:42 +00:00

Author

Owner

Possibly useful: http://twistedmatrix.com/pipermail/twisted-python/2007-May/015376.html

Possibly useful: <http://twistedmatrix.com/pipermail/twisted-python/2007-May/015376.html>

nejucomo commented

2014-08-23 21:14:52 +00:00

Author

Owner

There are important usability and security issues to consider. Daira just pointed out that a service shared across the system would need different alias files between users.

These issues are similar to those documented in #1665.

There are important usability and security issues to consider. Daira just pointed out that a service shared across the system would need different alias files between users. These issues are similar to those documented in #1665.

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1283

No description provided.