Groups > linux.debian.user > #203730

Re: e2fsck detail check

From	Jude DaShiell <jdashiel@panix.com>
Newsgroups	linux.debian.user
Subject	Re: e2fsck detail check
Date	2018-12-30 08:50 +0100
Message-ID	<xaE1b-3WN-1@gated-at.bofh.it> (permalink)
References	<xarx0-4EY-5@gated-at.bofh.it> <xaw3E-7D0-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Thanks much, highly informative.
On Sun, 30 Dec 2018, David wrote:

> Date: Sat, 29 Dec 2018 18:18:41
> From: David <bouncingcats@gmail.com>
> To: debian-user <debian-user@lists.debian.org>
> Subject: Re: e2fsck detail check
> Resent-Date: Sat, 29 Dec 2018 23:19:07 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
>
> On Sun, 30 Dec 2018 at 05:20, Jude DaShiell <jdashiel@panix.com> wrote:
> >
> > I have a question about the -c fd command line switch.  Would the valid
> > options for fd be stdin stdout and stderr?
>
> The file descriptor fd is a number. It is defined by the parent process.
> The parent process is typically the shell you use to start e2fsck
> interactively, or the shell script that starts e2fsck.
>
> You can read about file descriptors here:
> http://mywiki.wooledge.org/FileDescriptor
>
> The e2fsck man page also explains that if you precede the
> fd number with a minus sign, then e2fsck will defer writing to the
> file descriptor until it receives a SIGUSR1 signal. This is a
> extra feature specific to e2fsck that has nothing to do
> with file descriptors in general.
>
> You can read about signals here:
> http://mywiki.wooledge.org/SignalTrap
>
>

--

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

e2fsck detail check Jude DaShiell <jdashiel@panix.com> - 2018-12-29 19:30 +0100
  Re: e2fsck detail check Grzesiek Sójka <pld@sojka.co> - 2018-12-29 20:00 +0100
  Re: e2fsck detail check David <bouncingcats@gmail.com> - 2018-12-30 00:20 +0100
    Re: e2fsck detail check Jude DaShiell <jdashiel@panix.com> - 2018-12-30 08:50 +0100

csiph-web