I actually tried this (to disable IMAP), but I didn't restart inetd - so I guess that explains why moments latter I was greeted with the amber flashing <blink>DANGER-DANGER!!</blink> message.No, in fact, it will make it mad ;) I forgot about that miserable thing... I suppose it's no worse getting logs saying the imap server is dead as opposed to getting logs saying Idiot_Monitor can't log in, but ideally it would be better to figure out how to make the machine stop thinking imapis something you want running ;0 sub repair_cpu # Fix the CPU # Arguments: none # Side effects: none yet, what are we supposed to do return "1020 Repair of cpu not implemented";I was kind of hopeing imap check had a flag somewhere, but it appears to be 'wired in' :(gsh
Yep you're right... I thought I'd give it another try so I commented it out, then restarted inetd. It certainly closed the port, but good old amber glow whas flashing like the girls in the window across the street. :-P
So.... I pulled one of these numbers: cd /usr/admserv/html/.cobalt/images cp a_monitor_blink.gif a_monitor_blink.gif_bkup cp a_monitor_off.gif a_monitor_blink.gifAt least I don't have to see the DANGER thingy everytime I go into admin, and I can still check the status of different systems (disk, email, web, etc) in the monitor menu. I wonder if it'll fry that little 300Mhz sitting in there getting all cycled because I plugged IMAP up..? <g>.. Piss on it... I like it better without the open IMAP port.. :)
Craig _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com