2015/10/20 6:29 "Christoph R. Murauer" <n...@nawi.is>: > > Hello ! > > I readed the FAQ 4.8 about partioning my drive but have a little problem > of understanding. > > The machine has 32 GB physical RAM,
Wow. Way cool. > the disc is a 256 GB SSD That's not shabby, either. > (yes, I know, > I should not use swap on a SSD) Have you been reading this thread? http://marc.info/?t=144492611700013&r=1&w=2 > and, I installed the latest snapshot from > yesterday. So far so good. > > Disklabel likes to create in auto layout b: swap with 23,2 GB and e: /var > with 30,2 GB. > > If I follow the FAQ, then core dumps should not work. 2G RAM, 4G swap on my netbook running openbsd. I have lots of core dumps sitting around. I have not seen any the size of physical memory. Nothing close. Even firefox doesn't leave that much of a dump when it bombs. Hmm. Xombrero, from when I was playing with that, left a coredump of 512M. Firefox left one at 197M. Time to rm those. > I could resize swap > and /var to have the same (or bigger size) as the physical RAM which is > also no problem. My question - or better the things I don't understand (I > found no informations and also had no panic message till now) are, which > size had a core dump and, will core dumps work, if swap (on /var is enough > place to copy the core dump file from swap to /var/crash after a reboot) > is smaller then the physical RAM ? My question is meaned, that swap is > only used for core dumps - nothing more. So, you don't plan on using swap for deep sleep or powered-down system suspend? Why do you have 32G of RAM? What kind of working sets do you expect the applications you'll be running to have? Do you expect chain-reaction core dumps, where one application hits an uncaught exception and dumps core and then its parent or some other application that is communicating with it bombs and dumps core, too? In other words, do you expect to ever have all 32G filled with stuff that all at once dies and dumps core? > Thanks for your answers. > > Regards, > > > Christoph
