[ale] lost+found

[Jim]

Really? 
 
cd /part (assuming part is the mounted partition)

mkdir newdirectory
mv * newdirectory
mv newdirectory/lost+found .
edit /etc/apache/http.conf (or wherever the conf file is)
change
DocumentRoot "/part"
to
DocumentRoot "/part/newdirectory"
<
And change
<Directory "/part">
to
<Directory "/part/newdirectory">

Or if it's not the DocumentRoot, change the appropriate <Directory> entry.

That's what I meant by my statement.  Not a whole lot of work, IMHO.

Jim.


Randal Jarrett wrote:
> There is a little more needed than just creating a directory and I don't
> think that a link will work.
>
> make the directory, then run a shell script to create several hundred 
> (this is determined by how many files you have on the partition) files,
> then remove them.  This leaves the structure for fsck to write recovered
> files into.
>
> It doesn't take up much space but without it fsck cannot recover files.
>
>
>
> On Sat, 2006-12-16 at 10:43 -0500, Jim wrote:
>   
>> Jim Popovitch wrote:
>>     
>>> What happens if I delete lost+found on an ext3 partition?  Is it really
>>> necessary to have?
>>>
>>> Why?  It's a stable partition, rarely changing.  This partition is
>>> exposed via ftp and http, and as such some browsers and other tools try
>>> to "crawl" a level deeper for caching reasons.  The lost+found directory
>>> is owned solely by root, so ftpd and apache users don't have access...
>>> but my logs fill up with errors about their denied attempts.  
>>>
>>> -Jim P.
>>>
>>>   
>>>       
>> I can't say for sure what would happen, except I know fsck expects a
>> lost+found. Perhaps you can create a directory on that partition and
>> move everything (except lost+found) to that directory and point the
>> apache directory to it instead? It doesn't answer your question but it
>> will eliminate the errors.
>>
>> Jim.
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://www.ale.org/mailman/listinfo/ale
>>