[Leaplist] Lose server after a few hours....

[Bryan J. Smith]

Whit Hansell <skipper44 at comcast.net> wrote:
> Thanks for the info...  Mucho appreciated... You've got
> the experience and I have a biggo' need.

I just have my experience.  It's not always applicable,
and my APT/DPKG-based system experience is either dated
or based on far lesser usage than YUM/RPM-based systems.
Same goes for my reduced Portage/Ports-based experience
as well.

> I "skrew'd" up here.  I do NOT have a separate boot and
> root.  It's all root, with /boot inside /.

No, you didn't screw up.  I don't separate them either.
And it's a matter of preference anyway.

> And I increase the size of /, not /boot.

It's best to just make it "big enough."  Storage is so
cheap these days, and you only back up used sectors.  ;)

> My drive in the client is only a 20G and the server is a
> 40G, both IDE.  I didn't increase the size of the /
> directory too much when I increased the size because I was
> pulling from /usr, I think, and wanted it to have as much as
> possible cuz' no tellin' what I'll want to add
> at a later date.  Altho' I will say that Debian is doing
> a very good job of having a very interesting and fat package
> management inventory.  They're adding stuff all the
> time. 
> '***
> whit at brightsun:~$ df -h
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/hda1             373M  257M   97M  73% /
> tmpfs                 443M     0  443M   0% /lib/init/rw
> udev                   10M   96K   10M   1% /dev
> tmpfs                 443M     0  443M   0% /dev/shm
> /dev/hda9             9.0G  4.6G  4.0G  54% /home
> /dev/hda8             373M   11M  343M   3% /tmp
> /dev/hda5             4.5G  3.1G  1.2G  73% /usr
> /dev/hda6             2.8G  703M  2.0G  27% /var
> 192.168.0.102:/home/whit
>                       29G   17G   11G  62% /mnt/nfsd,
> '***

I'm really "big" on uniformity and consistency.

I like to make partitions on perfect multiples of two (2),
and slices of similiar sizes.

Which goes back to my logic ...

  2-4x RAM ~ swap = / = /tmp = /var

>From there, make /usr, /home (or /export/blah, etc...) a
multiple of that (either 1, 2, 4, etc...).  Now that's just
me.  LVM helps as well, because you can always increase
on-the-fly (although I put / outside of LVM, so / is
typically a large size -- at least 2x and possibly 4x RAM).

Sub-500MiB doesn't cut it with /root or /tmp these days.
And 2-3GiB is really small for /var with today's ops too.

> Problems in stable have occurred but as you say, rarely.  
> That's what surprised me that it came back after the
> next dis-upgrade.  That showed it was a bug in the prior
> dist-upgrade somewhere or at least that's where I
> believe the problem was.  But you are right, stable is
> usually very stable and not a problem.

I think it's because your /var has only 2G available.

Every package management system uses /var, and I'm fairly
certain all of them use /var/cache, or possibly /var/spool
or /var/tmp.

The /var directory is for storage of service**, operations and
other data that must be preserved during reboots.

**SIDE NOTE:  As of newer standards, /srv is actually the
directory for service data, long story.  Various distros have
not yet changed that though.


-- 
Bryan J Smith          Professional, Technical Annoyance
b.j.smith at ieee.org    http://www.linkedin.com/in/bjsmith
--------------------------------------------------------
I don't have a "favorite Linux distro."  I use, develop
and support community efforts, often built around Linux.
Technology and solutions are my focus, not dragging in
assumptions, marketing and other concepts which dominate
non-community developed software, which I left long ago.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.