Pruned the "older" breed from the UUG?? I'm still arround and no, I'm still not happy with the CS department for kicking us out 6 years ago for political reasons. If you can convice them to let you host there, though, more power to you. We've always been friends with the CSRs there... the problem is in the department management.... they don't want the liability of some "rogue" entity running their own system on the cs networks.
I wish you luck though perhaps they will have warmed up to students exercising initiative. Your hardware problems sound possibly like a processor overheating issue. What does the console say after the kernel panics? -matt On 27 Jan 2003, David Smith wrote: > -----Forwarded Message----- > > > From: Art Moore <[EMAIL PROTECTED]> > > To: David Smith <[EMAIL PROTECTED]> > > Subject: Re: Phantom: long term considerations > > Date: 27 Jan 2003 08:58:36 -0800 > > > > whats the uptime over the weekend? > > > > Yeah we need to have an officers meeting here to > > figure out all this stuff, and I still want to puch > > the install fest off one week. (Personal Reasons) > > > > Art > > > > --- David Smith <[EMAIL PROTECTED]> wrote: > > > Art/Byron: > > > > > > This new phantom box has some problems. Last time it > > > crashed there was > > > nothing in the logs to indicate why. That leads me > > > to believe that it was > > > a hardware problem. Anything else and we would have > > > seen some hints > > > leading up to it. This is a problem. Here are some > > > solutions: > > > > > > Very Short term: > > > > > > The first time it crashed, Phantom had been up for > > > just over 1 day. This > > > time it crashed after 1.5 days. Perhaps we should > > > setup a 12-hour cron job > > > to reboot the thing regularly. > > > > > > Short term: > > > > > > Find a new home for the box where we can have > > > quicker/easier access to it > > > for rebooting/diagnosing the problem. I've talked to > > > Andrew Jorgensen and > > > he thinks that he might (a big might) be able to get > > > us space in Jake's > > > old office (above the pendulum) if we provide a > > > switch. Additionally, he > > > might (a bigger might) be able to get us a key to > > > the room. Also, we have > > > contact in the Chemistry dept with Michael Torrie. I > > > think now that we > > > have "pruned" the older breed of UUG, we might be > > > able to approach the CS > > > department about it, which I think would be superior > > > to the other two > > > routes. Also, Dan Johnson has just been promoted and > > > replaced by a newer > > > fellow from Sun. This new guy might be a good point > > > of contact (he's my > > > boss's boss). Chew on those ideas and let me know > > > what you think. > > > > > > Long term: > > > > > > We've got to find the offending hardware (if it is > > > indeed a hardware > > > problem) and replace it. I'm thinking of the usual > > > suspects: power supply > > > or RAM. Could we get our hands on some diagnostics > > > tools and check those > > > things out? > > > > > > Sorry to bug you guys on a Saturday night. Man, this > > > week has been quite > > > buggy. :) > > > > > > --Dave > > > > > > > > > > __________________________________________________ > > Do you Yahoo!? > > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > > http://mailplus.yahoo.com > > > ____________________ > BYU Unix Users Group > http://uug.byu.edu/ > ___________________________________________________________________ > List Info: http://phantom.byu.edu/cgi-bin/mailman/listinfo/uug-list > -matt ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://phantom.byu.edu/cgi-bin/mailman/listinfo/uug-list
