On 05/15/2015 04:19 PM, Ted Byers wrote:
I am appending a list of the contents of /var/log. Is there a quick way to get rid of those logs that are, say, more than a month old
Two points: Yes, you can delete the *.xz. Manually. You may even want to compress log files more aggressively :-) You may also want to "tune" the generation of logs - see the appropriate config files, probably in /etc/ somewhere Secondly, why oh why oh why don't you have /var on a separate file system? Let me hark on about using LVM for managing file systems. Heck, if my /var grows I can make a new logical volume just for /var/log! I found that, for example, my photo collection was overloading /home. So I created a "Photographs" LV and mounted it at /home/anton/Photographs. In die course that grew so I now have appropriately sized LVs mounted at ~anton/Photographs/2012, ~anton/Photographs/2013, ~anton/Photographs/2014, ~anton/Photographs/2015. The key in the above sentence is "appropriately sized". I can do provisioning -- aka "shrink to fit" -- after the event. That lets me free up what would be wasted space and lets me grow, for example the ROOT LV if needed. In reality I don't need to because I have /dev/mapper/vgmain-vUsrShare on /usr/share /dev/mapper/vgmain-vOpt on /opt /dev/mapper/vgmain-vVar on /var /dev/mapper/vgmain-vSrv on /srv /dev/mapper/vgmain-vLocal on /usr/local /dev/mapper/vgmain-vTMP on /tmp /dev/mapper/vgmain-vDocuments on /home/anton/Documents /dev/mapper/vgmain-vDownloads on /home/anton/Downloads /dev/mapper/vgmain-vMail on /home/anton/Mail many of the things, particular under ~anton/, are on 5G LVs. That makes them easily mapped onto DVDs for backups. LVM also allows for snapshots of LVs which makes backup easier :-) In this day and age, dealing with hard drives or RAID arrays many times the size of what it takes to install the basic system[1] there is really no justification for NOT making used of the 'deferred provisioning' available with LVM. My desktop has a 1T 'drive' with /boot and /swap, which are easy to provision for, outside the LVM. I could, and have in the past, added swap with a LV, but don't at the moment. I could and have in the past had /boot as a LV but that can be problematic when doing crash recovery as you need to get the mapper running before you could mount it, and the "recovery" mechanism on the DVD doesn't know about that by default; it takes explicit manipulation - simpler to have a fixed /boot :-) So I have, logically, 924.06 GiB in the LVM with over 25 LVs (including ones dedicated to downloading and one dedicated to uploading from the camera) leaving about 700GiB free Adding LVs to deal with VM images, if you live with virtual machines, is very easy and convenient, as is duplicating them! Perhaps I've become slick with experience, perhaps its that I don't try complicated things like striping/mirroring of individual LVs. Creation, duplication, deletion, resizing of LVs (and corresponding file systems) is straight forward and easy. Fixed provisioning at install time is just so 20th century! [] I have older, slower, single core machines from the Closet of Anxieties with 30G drives on which I've installed openSuse and still have adequate space for running, for example, a LDAP server + SAMBA managing login authentication for a Windows domain + RADIUS + NIS -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org