Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-03 Thread andrew mcelroy
On Sun, Mar 3, 2013 at 12:54 AM, James Sizemore yame...@gmail.com wrote: But anyone that has a system that must stay up who needs maximum uptime or deals with valuable data should configure there systems to take system cores on crash. Even if you don't have a vendor contract. You can pay for

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread Michael Chaney
Wow, amazing how much I've forgotten in 15 years. So, yes, other issues are # of inodes (another way you can fill a disk up), security (you can fill /var but you can't fill the whole disk), and backups. Backups were the other big reason that we split stuff up functionally as I showed above.

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread Jonathan Sheehan
On Sat, Mar 2, 2013 at 9:10 AM, Michael Chaney mdcha...@michaelchaney.com wrote: Backups were the other big reason that we split stuff up functionally as I showed above. Basically, /home (or /usr/home) was the only thing that had to be backed up regularly. So, we haven't mentioned what used

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread Kent Perrier
IMO, this issue speaks to the weakness of the linux LVM. If you could dynamically shrink over-sized file systems to move the space around in the volume group as utilization patterns change (or become apparent) then this would not be an issue. /var is too small and you have tons of space in

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread Tilghman Lesher
On Sat, Mar 2, 2013 at 2:17 PM, James Sizemore yame...@gmail.com wrote: I'll have to disagree with Tilghman on this one. You should always have at least as much swap as ram, however double would be over kill. If for no other reason than to guaranty you get a full core dumps on system

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread andrew mcelroy
On Sat, Mar 2, 2013 at 7:12 PM, Tilghman Lesher tilgh...@meg.abyt.es wrote: On Sat, Mar 2, 2013 at 2:17 PM, James Sizemore yame...@gmail.com wrote: I'll have to disagree with Tilghman on this one. You should always have at least as much swap as ram, however double would be over kill. If for

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread Tilghman Lesher
On Sat, Mar 2, 2013 at 7:12 PM, Tilghman Lesher tilgh...@meg.abyt.es wrote: On Sat, Mar 2, 2013 at 2:17 PM, James Sizemore yame...@gmail.com wrote: I'll have to disagree with Tilghman on this one. You should always have at least as much swap as ram, however double would be over kill. If for

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread Jack Coats
I found the old SOLARIS rule of thumb of 2xMemory as swap is a good minimum for 'normal' uses. The idea is you NEVER want to run out of memory (swap included) or the kernel makes some ugly decisions. Real needs depend on your application. CAD users or big matrix manipulations, or large

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread James Sizemore
First a little history, I manage 10,000 Unix systems (as part of the Break/Fix group) for a large international bank. So I am a little sensitive to lack of core dumps or failed core dumps. As not having them makes my job a pain. About a third of these are Linux. The problem with using

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread Tilghman Lesher
On Sat, Mar 2, 2013 at 8:17 PM, James Sizemore yame...@gmail.com wrote: First a little history, I manage 10,000 Unix systems (as part of the Break/Fix group) for a large international bank. So I am a little sensitive to lack of core dumps or failed core dumps. As not having them makes my

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-02 Thread James Sizemore
System cores find issue with failing hardware and kernel bugs not just experimental hardware. In my environment any outage or crash has to have a root cause analysis. With high volume trading systems, and financial transaction systems. we simply can't reboot and move on. Every effort must be

[nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread Howard White
Would you believe /var is full. ~!@#$%^ Howard -- -- You received this message because you are subscribed to the Google Groups NLUG group. To post to this group, send email to nlug-talk@googlegroups.com To unsubscribe from this group, send email to nlug-talk+unsubscr...@googlegroups.com

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread Kevin Hart
To Howard. Yea sometimes the simple answer is to do df -h :). I had one yesterday that after an hour figured out the nic was running half duplex with tons if collisions. Shoulda picked up on that sooner. As to Curt I agree. Back when home was where people wrote to people wanted to save that. But

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread David R. Wilson
Yes... You hit on exactly the problem. When /var fills up your hosed. That is a good reason to have a separate var partition. you might be able to log in as root and move things off. Since it is on a common partition with everything else, someone else would have to chime in with a way to mount

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread Kevin Hart
Or you just have some quality nagios monitoring setup so it alerts you on disk space. Or even a log watch email that you look at from time to time. I've never been locked out of any system in the last ten years because of space issues. Though I would find out why something is so chatty to make

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread Curt Lundgren
I don't know about less likely - for me it's more that the average disk drive has vastly more space than when it made sense to have protective partitions. We remember entire systems that had 300 MB drives, perhaps less. It was easy to tip the scales at that point. On Fri, Mar 1, 2013 at 5:16

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread Rob Huffstedtler
On Fri, Mar 1, 2013 at 6:22 PM, Curt Lundgren verif...@gmail.com wrote: I don't know about less likely - for me it's more that the average disk drive has vastly more space than when it made sense to have protective partitions. We remember entire systems that had 300 MB drives, perhaps less.

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread David R. Wilson
Hello Howard, It doesn't hurt to have a separate /var and /var/log partition. At least then you can go trim logs, or errant web stuff (which I have seen happen). It is a bit more of a problem when initially loading the box, but that is likely not a major problem. You might be able to add

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread Michael Chaney
I used to cut them up functionally so that various parts of the system were all limited to a reasonable amount of disk space. Practically speaking, that means the root, /tmp, /var, and /home were on their own partitions. I would typically put /usr on its own, also, simply because most installed

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread John F. Eldredge
Michael Chaney mdcha...@michaelchaney.com wrote: I used to cut them up functionally so that various parts of the system were all limited to a reasonable amount of disk space. Practically speaking, that means the root, /tmp, /var, and /home were on their own partitions. I would typically

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread Jack Coats
'in the day' we ran programs using chron regularly to check things like file system full, etc, and sometimes take action if things were overly full. /tmp and /var are pretty normal to fill up, but if / fills, you get into deeper pookie. That is why there is a reserve limit that allows root to

Re: [nlug] OHHH FIRETRUCK!!!!!

2013-03-01 Thread Tilghman Lesher
On Fri, Mar 1, 2013 at 6:11 PM, Rob Huffstedtler rhuffstedt...@gmail.com wrote: On Fri, Mar 1, 2013 at 6:22 PM, Curt Lundgren verif...@gmail.com wrote: I don't know about less likely - for me it's more that the average disk drive has vastly more space than when it made sense to have