uptime
doing
ground covered
signals ignored
file returnedno
watching
not started. no process, no dog, nothing to report.
pid 1174  ·  state D  · 

currently

nothing running
processfetch
pid1174
stateD · uninterruptible
controlling ttynone
arguments givennone
ground covered
times it has stopped
file returnedno

the tape · newest first

brought back · none of it the file

nothing yet.

time spent

process table

signals · sent to a process in state D

address space · /proc/1174/maps

0x00000000004000000x00007ffffffde000
the heap grows. the stack holds. the region reserved for the file has been reserved the whole time, and nothing has ever been mapped into it.

shell · it will not help

$

strace · -p 1174

not attached. nothing to trace.

fetch(1) · general commands manual

NAME
     fetch — retrieve a file. eventually.

SYNOPSIS
     fetch [file]

DESCRIPTION
     someone ran fetch. a dog came out instead. it went to get the
     file. that was some time ago.

     fetch takes no arguments and was given none. it does not know
     which file. it knows what finding one feels like, which is the
     only part of the job it has ever been sure about.

     it stops often. it is not lost. it has simply found something
     else, and something else is still something.

OPTIONS
     none. it does not take options. it has been offered options
     before and it did not use them.

EXIT STATUS
     fetch has not exited.

SIGNALS
     the process is in state D. it is not ignoring your signals, it
     is not receiving them. SIGKILL included. this is not a decision
     it has made and it would like that understood.

BUGS
     will not drop it.

SEE ALSO
     cat(1), read(2), wait(2), kill(1) (will not help)