Re: fsck SIGINFO

To: tech-userlevel%NetBSD.org@localhost
Subject: Re: fsck SIGINFO
From: Mouse <mouse%Rodents-Montreal.ORG@localhost>
Date: Mon, 7 Jan 2013 23:28:42 -0500 (EST)

> Some churn about a decade ago caused fsck_ffs to print pass1 siginfo
> messages to stdout, rather than to stderr like all the other passes
> do.

Shouldn't they go to /dev/tty?  That's effectively where the kernel's
messages go, as far as I can tell.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

Follow-Ups:
- Re: fsck SIGINFO
  - From: Alan Barrett

References:
- Re: fsck SIGINFO
  - From: Taylor R Campbell

Prev by Date: Re: Should we use _malloc_prefork and _malloc_postfork?
Next by Date: Re: Should we use _malloc_prefork and _malloc_postfork?
Previous by Thread: Re: fsck SIGINFO
Next by Thread: Re: fsck SIGINFO
Indexes:

Home | Main Index | Thread Index | Old Index