From: mrtuxa <mrtuxa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Virt-Manager Not Connected
Date: Mon, 02 Jan 2023 10:13:47 +0100 [thread overview]
Message-ID: <20230102091347.RT0yR53jll93jSF4D200rjA16IY0XonsMMR9xbk7JNc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41397@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
New comment by mrtuxa on void-packages repository
https://github.com/void-linux/void-packages/issues/41397#issuecomment-1368765250
Comment:
> > how can i check if the service is running correctly
>
> You can check status of services with `sv status`. All running services are present in `/var/service` in the form of symbolic links.
> > how can i check if the service is running correctly
>
> You can check status of services with `sv status`. All running services are present in `/var/service` in the form of symbolic links.
```
[root@mrtuxa mrtuxa]# sv status dbus
run: dbus: (pid 861) 200s
[root@mrtuxa mrtuxa]# sv status libvirtd
run: libvirtd: (pid 866) 205s; run: log: (pid 865) 205s
[root@mrtuxa mrtuxa]# sv status virtlockd
run: virtlockd: (pid 864) 209s; run: log: (pid 863) 209s
[root@mrtuxa mrtuxa]# sv status virtlogd
run: virtlogd: (pid 880) 211s; run: log: (pid 878) 211s
```
next prev parent reply other threads:[~2023-01-02 9:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 20:03 [ISSUE] " mrtuxa
2023-01-01 20:04 ` classabbyamp
2023-01-01 21:06 ` realcharmer
2023-01-01 21:06 ` realcharmer
2023-01-01 21:06 ` realcharmer
2023-01-01 21:07 ` realcharmer
2023-01-01 22:00 ` mrtuxa
2023-01-01 22:00 ` mrtuxa
2023-01-01 22:05 ` classabbyamp
2023-01-01 22:08 ` realcharmer
2023-01-02 9:12 ` mrtuxa
2023-01-02 9:13 ` mrtuxa [this message]
2023-01-02 9:16 ` realcharmer
2023-01-02 11:04 ` mrtuxa
2023-01-02 11:50 ` paper42
2023-01-02 13:48 ` mrtuxa
2023-01-02 13:50 ` realcharmer
2023-01-15 1:51 ` bugcrazy
2023-04-15 1:52 ` github-actions
2023-04-29 1:52 ` [ISSUE] [CLOSED] " github-actions
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=20230102091347.RT0yR53jll93jSF4D200rjA16IY0XonsMMR9xbk7JNc@z \
--to=mrtuxa@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).