unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: Caleb Ristvedt <caleb.ristvedt@cune.org>, 24684@debbugs.gnu.org
Subject: bug#24684: invalid command-line syntax to herd causes a kernel panic?
Date: Thu, 13 Oct 2016 20:03:13 +0000	[thread overview]
Message-ID: <87inswow3i.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <CAELvotygpHU1F6-O_-L3cKrQ-JoAnGyWraLZDNS=KMxuwAd-3A@mail.gmail.com>

Hi,

many thanks again for finding this bug, this looks really important.

Caleb Ristvedt <caleb.ristvedt@cune.org> writes:

> I should have read the man page before trying to use multiple commands at
> once, but somehow it ended up causing a kernel panic?
>
> Here's what I ran as root in tty0 (I think that's what it's called, it's
> the thing I get to by pressing ctrl + alt + f1):
>
> herd enable ntpd start ntpd
>
> ntpd had been disabled because it kept immediately exiting, which it was
> doing because I had another one running, which I had running because it was
> originally disabled because it couldn't fix time errors of over 1000
> seconds without the -g flag and so immediately exited every time and was
> disabled by shepherd automatically. I don't know how relevant any of that
> is.
>
> On GuixSD
> can't-see-the-version-number-right-now-because-it's-panicked-but-I-think-it's-the-latest-one.

I can replicate this:

on my live-to-crash system in my network, running GuixSD on git commit
f803f775d244b4e3975ab42b9610d12b94f6e958

Screenshot the lazy way, cropped down to 1000xsomething:
https://quitter.se/notice/7658920

  reply	other threads:[~2016-10-13 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 19:26 bug#24684: invalid command-line syntax to herd causes a kernel panic? Caleb Ristvedt
2016-10-13 20:03 ` ng0 [this message]
2016-10-16 13:52 ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87inswow3i.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=24684@debbugs.gnu.org \
    --cc=caleb.ristvedt@cune.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).