🚀 go-pugleaf

In article <slrng5k08e.4ah.felixk@carrot.cabbage.patch>,
Felix Karpfen  <felix@spodzone.org.uk> wrote:
>I have recently paid my first visit to my "lost+found" directory.  The
>contents were an eye-opener.
>
>It turned out that the directory currently contains 83 files that occupy
>3.22 Mb.
>
>The files that are readable appear to be downloaded web-pages.  However
>many entries have 0 size and the following descriptions:
>
>>srw------- 1 felixk root         0 2008-06-09 18:10 76809616
>>srw------- 1 felixk root         0 2008-06-09 18:07 76809602
>>srw------- 1 felixk root         0 2008-06-09 18:06 75662599
>>srw------- 1 felixk root         0 2008-06-09 18:06 75547033
>>srw------- 1 felixk root         0 2008-06-09 18:06 75500994
>>srw------- 1 felixk root         0 2008-03-18 08:21 76743295
>>srw------- 1 felixk root         0 2008-03-18 08:03 75584621
>
>My attempts to find out the meaning of "s" (sticky?) failed miserably. 

Socket special files.  Easy way to find out would be "file 75584621"
or whatever.  These are a communication point, typically used to
talk to a daemon process.  E.g. /var/run/cups/cups.sock lets cups
clients talk to the cups daemon.

>My (very out-of-date) Linux text book said - see "man ls"; "man ls"
>said see "info ls".  And "info ls" is not included in the Debian Etch
>default install.

Can be a challenge finding where these things are documented, but
"file" is often helpful when trying to work out what a file is.

And it's not good to be finding things in lost+found.  That indicates
some level of file system corruption -- perhaps due to yanking the
power cord rather than shutting down cleanly.

Have fun,

Robert.
-- 
Robert Swan		| No, not the antarctic adventurer.
swan.r.l@gmail.com	| No, not the Canberra porn monger.
			| Yes, that's right, the boring one.