From: jfcolom <jfcolom@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Service "deluged" won't get/set its config files from /var/lib/deluge/.config/deluge but from /root/.config/deluge
Date: Mon, 28 Jun 2021 12:51:32 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31690@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
New issue by jfcolom on void-packages repository
https://github.com/void-linux/void-packages/issues/31690
Description:
### System
* package:
*deluge-2.0.3_10
### Expected behavior
`deluged` service should start up with `deluge` system user, and therefore, get/set its configuration files from /var/lib/deluge/.config/deluge
### Actual behavior
It is starts with `root` and, therefore, it gets/sets the configuration from /root/.config/deluge. As it cannot write there after that, there are some permission errors and it does not start properly.
### Workaround
In `/etc/sv/deluged/run`, replace
`exec deluged -d -U deluge -g deluge ${OPTS} 2>&1`
by
`exec chpst -u deluge:deluge deluged -d -U deluge -g deluge ${OPTS} 2>&1`
next reply other threads:[~2021-06-28 10:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 10:51 jfcolom [this message]
2021-06-29 1:16 ` sgn
2021-07-01 1:38 ` [ISSUE] [CLOSED] " sgn
2021-07-01 5:38 ` jfcolom
2021-08-05 19:19 ` q66
2021-08-05 19:22 ` q66
2021-08-06 2:49 ` sgn
2021-08-08 4:11 ` sgn
2021-08-08 4:12 ` [ISSUE] [CLOSED] " sgn
2021-08-18 10:46 ` jfcolom
2021-08-18 10:49 ` jfcolom
2021-08-18 10:53 ` jfcolom
2021-08-18 10:54 ` sgn
2021-08-18 10:54 ` sgn
2021-08-18 10:55 ` jfcolom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31690@inbox.vuxu.org \
--to=jfcolom@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).