From: ipkalm <ipkalm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: v2ray: add `run` to launch command for v2ray>=5.1.0
Date: Mon, 16 Jan 2023 06:54:19 +0100 [thread overview]
Message-ID: <20230116055419.r4FhsxcY8D9UMghK8SeVLQoBhwpfUek7r2Y6I7rGzE4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41430@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
New comment by ipkalm on void-packages repository
https://github.com/void-linux/void-packages/pull/41430#issuecomment-1383525940
Comment:
@kruceter it came from `help` command.
```
[root@void ~]# v2ray help
A unified platform for anti-censorship.
Usage:
v2ray <command> [arguments]
The commands are:
run run V2Ray with config
api call V2Ray API
convert convert config files
test test config files
tls TLS tools
uuid generate new UUID
verify verify if a binary is officially signed
version print V2Ray version
Use "v2ray help <command>" for more information about a command.
Additional help topics:
config-merge config merge logic
format-loader config formats and loading
Use "v2ray help <topic>" for more information about that topic.
```
If you try launch without `run` it will crash:
```
[root@void ~]# chpst -u _v2ray v2ray -config=/etc/v2ray/config.json
flag provided but not defined: -config
Usage of v2ray:
```
If add `run` all will be ok:
```
[root@void ~]# chpst -u _v2ray v2ray run -config=/etc/v2ray/config.json
V2Ray 5.1.0 (v2ray) 1672773149 (go1.19.4 linux/amd64)
A unified platform for anti-censorship.
```
next prev parent reply other threads:[~2023-01-16 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 0:58 [PR PATCH] " ipkalm
2023-01-16 4:19 ` kruceter
2023-01-16 5:54 ` ipkalm [this message]
2023-01-16 5:56 ` ipkalm
2023-01-16 6:39 ` kruceter
2023-01-16 8:06 ` [PR PATCH] [Merged]: " sgn
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=20230116055419.r4FhsxcY8D9UMghK8SeVLQoBhwpfUek7r2Y6I7rGzE4@z \
--to=ipkalm@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).