From: zmudc <zmudc@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] tigervnc: update to 1.13.1, add service directory
Date: Sat, 29 Jul 2023 19:15:53 +0200 [thread overview]
Message-ID: <20230729171553.B71gyqVESJljG5vmCbjd0Ps90GeY_sp1ViK6RHWmCJc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45307@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
New review comment by zmudc on void-packages repository
https://github.com/void-linux/void-packages/pull/45307#discussion_r1278343336
Comment:
The automatic log service creation did not pull in the correct service name, i.e., it was -t vncserver-1 for display 2, so I added the run file for the log service to ensure the logs for vncserver are tagged as vncserver-2, not vncserver-1. I think to do it your way, I will not be able to use just a symbolic link to the run script of vncserver for vncservers on other displays. I will experiment with some other approaches, perhaps without using symbolic links to the run service of vncserver for the other displays. I was using the technique used in the agetty-ttyN services here, but I guess that is not appropriate now?
next prev parent reply other threads:[~2023-07-29 17:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 6:11 [PR PATCH] " zmudc
2023-07-29 16:21 ` [PR REVIEW] " classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:21 ` classabbyamp
2023-07-29 16:46 ` zmudc
2023-07-29 16:56 ` zmudc
2023-07-29 16:59 ` zmudc
2023-07-29 17:01 ` zmudc
2023-07-29 17:09 ` [PR REVIEW] " zmudc
2023-07-29 17:15 ` zmudc [this message]
2023-07-29 17:17 ` zmudc
2023-07-29 17:20 ` zmudc
2023-07-30 19:27 ` [PR PATCH] [Updated] " zmudc
2023-07-30 19:57 ` zmudc
2023-07-30 22:39 ` zmudc
2023-07-30 22:48 ` zmudc
2023-07-30 22:48 ` zmudc
2023-07-30 23:31 ` [PR REVIEW] " zmudc
2023-07-30 23:32 ` zmudc
2023-07-30 23:33 ` zmudc
2023-07-30 23:34 ` zmudc
2023-07-30 23:39 ` zmudc
2023-07-30 23:46 ` zmudc
2023-07-31 2:05 ` zmudc
2023-07-31 2:38 ` [PR PATCH] [Updated] " zmudc
2023-07-31 2:49 ` zmudc
2023-07-31 3:43 ` [PR PATCH] [Updated] " zmudc
2023-08-01 0:07 ` zmudc
2023-08-01 0:10 ` zmudc
2023-08-07 15:16 ` zmudc
2023-08-11 2:48 ` zmudc
2023-08-11 2:56 ` zmudc
2023-08-17 19:33 ` [PR PATCH] [Updated] " zmudc
2023-08-17 19:46 ` ahesford
2023-08-17 19:56 ` [PR PATCH] [Updated] " zmudc
2023-08-17 20:00 ` zmudc
2023-08-17 20:00 ` [PR PATCH] [Closed]: " zmudc
2023-08-17 20:02 ` zmudc
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=20230729171553.B71gyqVESJljG5vmCbjd0Ps90GeY_sp1ViK6RHWmCJc@z \
--to=zmudc@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).