From: Andreas Enge <andreas@enge.fr>
To: Gottfried <gottfried@posteo.de>
Cc: Chris Keschnat <chris@catsu.it>, help-guix@gnu.org
Subject: Re: Virtualisation: Network problems
Date: Sat, 1 Oct 2022 15:32:31 +0200 [thread overview]
Message-ID: <YzhBb7QV2wvlozS8@jurong> (raw)
In-Reply-To: <35aae352-02cb-d346-4d61-9ac4650b2d84@posteo.de>
Am Mon, Sep 26, 2022 at 06:05:31PM +0000 schrieb Gottfried:
> gfp@Tuxedo ~$ ps -ef | grep virtlog
> it comes up with:
> gfp 5233 5218 0 19:45 pts/0 00:00:00 grep --color=auto virtlog
> (the word "virtlog" is in red colour)
> I don't know if that means virtlogd is running?
Answering a bit late (and only this question, since I know nothing about
virtualisation): It means that virtlogd is not running. It shows only
the process you started, which is "grep", with "virtlog" as a parameter.
As an example:
$ ps -ef|grep shepherd
root 1 0 0 11:37 ? 00:00:01 /gnu/store/cnfsv9ywaacyafkqdqsv2ry8f01yr7a9-guile-3.0.7/bin/guile --no-auto-compile /gnu/store/cdc1gzbp3q15kdiwn2i5j3437jwx61ac-shepherd-0.9.2/bin/shepherd --config /gnu/store/17vm5kngzkp3cvp0difp1plxm3dzp49k-shepherd.conf
andreas 9255 1334 0 15:31 pts/1 00:00:00 grep --color=auto shepherd
So there is one line about grep, of no interest; and one line showing that
the thing I am interested in, in this case shepherd, is running.
Andreas
next prev parent reply other threads:[~2022-10-01 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 15:47 Virtualisation: Network problems Gottfried
2022-09-26 16:29 ` Chris Keschnat via
2022-09-26 18:05 ` Gottfried
2022-10-01 13:32 ` Andreas Enge [this message]
2022-10-02 12:47 ` Tobias Geerinckx-Rice
2022-09-27 4:26 ` Chris Keschnat via
2022-09-28 13:08 ` can not boot again VM with tails Gottfried
2022-09-28 14:27 ` Felix Lechner via
2022-09-28 20:59 ` Gottfried
-- strict thread matches above, loose matches on Subject: below --
2022-10-03 11:23 Virtualisation: Network problems Gottfried
2022-09-27 19:02 Gottfried
2022-09-25 17:58 Gottfried
2022-09-26 4:19 ` Chris Keschnat via
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=YzhBb7QV2wvlozS8@jurong \
--to=andreas@enge.fr \
--cc=chris@catsu.it \
--cc=gottfried@posteo.de \
--cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.