I guess I whined about rebooting before, but today was just really uncool: there was a power cut at work, and of course I had about 10 virtual terminals open running various things (all in GNU screen). There were a few tens of editor swap-files to recover (I’m using the vim editor), but that’s actually the straightforward part. The really bad part is that between 10 or so bash shells, you really lose a lot of lines of unsaved command history – especially when your machine has been up for a month or two (sorry, I know that doesn’t sound very green, but at least it is not usually idling… and I guess I’ll switch my lights off tomorrow to find absolution).
Wait. I believe this may be the third post I’m sharing with the Ubuntu Weblogs community, and I still haven’t properly said hello. Someone’s acting like a caveman here…
Hello all! I’m just a happy free-software user (or did I mean open-source? I still haven’t made up my mind on this), there’s not much more to say. I’m very fortunate to be working on a physics PhD, which means that I get to play with GNU/Linux at work as well as at home.
If you don’t mind me complaining some more about reboots: the second mini-disaster today was that my laptop – also with maybe a dozen screen sessions – froze on resume from suspend, and I couldn’t remember the whole elephant thing. My laptop hadn’t seen a reboot in ages either, but at least a hundred succesful suspend/resume cycles since then, so this was unexpected.
Anyway, I now have no idea, no recollection whatsoever, what I’ve been doing or working on the past few days :)
To better deal with this kind of stuff in the future, I’ve already found out that I can save my bash history to disk whenever I want using “history -a”. Now if I may ask my dear readers:
- is there any way to make a shell session “persistent” (I guess as if snapshotting memory) to some extent?
- would you perhaps know a tutorial that shows me how to begin debugging such very sporadic lock-ups on resume? Where do I start – in syslog?