Github messages for voidlinux
 help / color / mirror / Atom feed
From: mobinmob <mobinmob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: monkey: fix the runit service.
Date: Fri, 19 Mar 2021 19:18:12 +0100	[thread overview]
Message-ID: <20210319181812.3M-fD0NZ9tyofFEoIu6mwFCfamliEApXPXsdxcUL6uA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29575@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]

New comment by mobinmob on void-packages repository

https://github.com/void-linux/void-packages/pull/29575#issuecomment-803022327

Comment:
I found the problem while creating a [66 service for monkey](https://github.com/mobinmob/void-66-services/pull/81/files). I followed the runit service, but I got permission issues in the log indicating that the daemon was not able to create necessary files - which is understandable, because there is no `monkey` user. When reading the configuration file, I came across this:

```
# User:
    # -----
    # If you want the webserver to run as a process of a defined user, you can
    # define it in this variable. For the change of user to work, it's necessary
    # to execute Monkey with root privileges. If it's started by a user that
    # that doesn't have root privileges, this variable will be omitted.

    User _monkey
```
I have no reason to doubt the validity of the comments which also exist in the official [documentation](http://monkey-project.com/documentation/1.6/configuration/server.html). A cursory check with ps also confirms that the daemon runs from the `_monkey` user.


  parent reply	other threads:[~2021-03-19 18:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 22:54 [PR PATCH] " mobinmob
2021-03-19 17:50 ` ericonr
2021-03-19 18:18 ` mobinmob [this message]
2021-03-19 18:25 ` [PR PATCH] [Updated] " mobinmob
2021-03-19 18:25 ` [PR PATCH] [Merged]: " ericonr
2021-03-19 18:25 ` ericonr

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=20210319181812.3M-fD0NZ9tyofFEoIu6mwFCfamliEApXPXsdxcUL6uA@z \
    --to=mobinmob@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).