View Issue Details

IDProjectCategoryView StatusLast Update
0005929Talerdeployment and operationspublic2019-10-16 17:28
ReporterFlorian DoldAssigned Tong0 
PriorityhighSeverityfeatureReproducibilityN/A
Status resolvedResolutionreopened 
Product Version 
Target VersionFixed in Version 
Summary0005929: have a reliable way to start BB workers and master
DescriptionCurrently we start them manually. This means, though, that after a restart, these services will be down.

Maybe systemd user units are appropriate for this? We want to avoid needing to be "root" for administering these services.
TagsNo tags attached.

Activities

ng0

2019-10-15 13:36

developer   ~0015015

system user files sounds good enough, I'll explore if this works or apply another solution.

ng0

2019-10-16 10:26

developer   ~0015016

Last edited: 2019-10-16 16:46

View 3 revisions

Correction, for the record (and notes for myself): unless my information is too old, systemd user units only exist as long as a session of that user exists (and only start to exist once the user logs in). We want https://www.freedesktop.org/software/systemd/man/loginctl.html for that. user units + loginctl are what could get the job done.



- we also have to check if we need to add XDG_RUNTIME_DIR=/run/user/$UID to the environment before next reboot

Florian Dold

2019-10-16 14:35

manager   ~0015017

You can configure systemd so that user units linger!

See here https://wiki.archlinux.org/index.php/systemd/User (search under the keyword linger).

Issue History

Date Modified Username Field Change
2019-10-15 09:03 Florian Dold New Issue
2019-10-15 09:03 Florian Dold Status new => assigned
2019-10-15 09:03 Florian Dold Assigned To => ng0
2019-10-15 13:36 ng0 Status assigned => acknowledged
2019-10-15 13:36 ng0 Note Added: 0015015
2019-10-16 10:26 ng0 Note Added: 0015016
2019-10-16 10:27 ng0 Note Edited: 0015016 View Revisions
2019-10-16 14:35 Florian Dold Note Added: 0015017
2019-10-16 14:35 Florian Dold Status acknowledged => assigned
2019-10-16 15:35 ng0 Status assigned => resolved
2019-10-16 15:35 ng0 Resolution open => fixed
2019-10-16 15:36 ng0 Status resolved => feedback
2019-10-16 15:36 ng0 Resolution fixed => reopened
2019-10-16 16:46 ng0 Note Edited: 0015016 View Revisions
2019-10-16 17:28 ng0 Status feedback => resolved