david <[EMAIL PROTECTED]> writes:
> On Thu, 2008-07-17 at 10:11 +1000, Tony Sceats wrote:
>> > Ah, now this all depends. If /var/run was a normal disk filesystem
>> > under Ubuntu you would be correct. It isn't, though:
>> >
>> > ] mount | grep /var/run
>> > varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
>> >
>> > Note 'type tmpfs' there? tmpfs is a swap backed ramdisk, essentially,
>> > and like /var/lock is put there by Ubuntu to ensure that these
>> > directories are cleaned at reboot without having to fuss about deleting
>> > files or read-only filesystems.
[...]
> Now please excuse my ignorance, but that makes it sound as if Ubuntu's
> /var/run is actually held in RAM, and not on disk at all?
It is.
> My system is a clean install of Hardy server and the install didn't
> ask for a size for /var/run so it must have been automated. There is
> 4G of Ram, so if the memory is allocated as needed, then 2G makes some
> sense if /var/run is used for performance reasons.
It should be limited to half the size of your ram, which is the default
limit for tmpfs.
> The problem only arises with apps like mondo that assume /var/run will
> be large. I haven't seen the problem before. I used mondo on Feisty
> and Sarge and the question never arose.
Feisty backed /var/run with tmpfs, IIRC, though I don't have an install
on hand. Anyway, mondo /shouldn't/ be using that path. It is wrong, in
many ways, and what they really want is /var/tmp, or /tmp.
(Well, or /var/{cache,lib,spool}/mondo, I guess, depending on exactly
what is being written there.)
Regards,
Daniel
> Given that there is an option in mondoarchive to specify another path,
> should I report this as a bug? It kept me busy for several hours before
> the penny dropped as to why I was getting disk full errors.
>
> David.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
