Dactyl’s Health

Posted by Nathaniel.

Frankly, I don’t think dactyl is in good health and I don’t know what’s wrong. So, if you go to see the blog one day and nothing comes back, just wait a little while.

Dactyl is set to reboot automatically in the case of a kernel panic, but the issue we’re currently having is something less than a kernel panic but something more than nothing. Cron still works when things die, so I’ve set a cron job to reboot the computer at noon every day. It’s not ideal, but at least things will recover.

If you, gentle reader, happen to be up at Dartmouth and have some free time in the next couple of weeks, there are some things you can do to perhaps fix the problems. It would be good if someone could actually look at dactyl’s motherboard and make sure nothing is chock full of dust leading to overheating. Or, for someone supercool, you could connect a monitor to the computer and see what it actually says during a crash.

If you want to help, let me know.

  

3 Responses to “Dactyl’s Health”

  1. Jules Says:

    I’m willing to help, but I won’t be back in Hanover until Jan. 16. I’ll check back with you then.

  2. Nathaniel Says:

    Jules, I might just take you up on that. I’m really hoping that it’s a software problem that I can fix remotely, but I’m short on ideas at the moment and it might take someone there.

    In other news, are you going to the AAS?

  3. Jules Says:

    I’m actually not going to the AAS. I’m going observing for 2 weeks. It’s going to be a long run on KP. Hopefully there will be some cool people out there. haha…

Leave a Reply