<snip>
Yes, you do need. Log in on the admin web and look ad BlueLinq / Settings /> Strange, my blue link has never worked correctly. Instead all blue linkI have not configured anything for that. It should still be set to it's
> notices end up as a dead.letter in /root?
hmmmmmmmmmm... did you configure the email notification correctly? Have
you looked at these files? What is the recipient of the dead letters?
default of admin.
In reality emails are being sent to
?ISO-8859-1?Q?admi?= <admi>
What ever that is. Now all other email notification works fine. For
example a fan failed a while back, I got an email and replaced the fans.
I also get other admin type emails, so everything should be configured
correctly.
I was not aware that you needed to do anything special for Blue Link to
email you?
Basic and enter the address where the notifications should be mailed to.
I set the query schedule to daily, just to get information as quick as
possible.
the BlueLinq works on all my three XTRs ... you should check yourIt's really not a big deal. I have other software I am always checking to see if I need to upgrade it, that is not part of the Cobalt Distro.
configuration
<snip>
I will have to look into Qmail. It's supposed to be better with SpamI made really good experiences with qmail. It's quite easy to install and
which is driving me nuts. It's hard enough for me to relay real mail
through my XTR, but the rest of the spammers have no problem. I have a
spam list upward of 1000 entries, and growing daily.
The volume of spam emails has gone down, but still a headache.
and i never heard that a properly configured / installed qmail was ever
hacked. You should check out
http://cr.yp.to (the site of D.J. Bernstein the developer of qmail)
http://www.qmail.org
http://www.lifewithqmail.org
http://www.flounder.net/qmail/qmail-howto.html
Yeah, i had some more funny messages like "lost interrupt" and also this:> What services are you using on the XTR? Mail, FTP, Web, Db,etc.
Web, Mail
> What is your average load, CPU & more importantly memory?
> What do you mean by crash. Kernel/Machine locking up becoming
> unresponsive? Spontaneous re-boots, blue screen of death ;)
all of that (no joke!)Wow, I have never seen Linux spontaneously re-boot. The only times I have seen Linux lock up is with certain programs like Quake under X, which usually can be over come. I seem to remember one other time that a Linux machine became unresponsive, but it was hardware/driver related which is kernel level.
Dec 17 00:01:26 cobalt3 kernel: hdg: write_intr error1: nr_sectors=1, stat=0xd0
Dec 17 00:01:26 cobalt3 kernel: hdg: write_intr: status=0xd0 { Busy }
Dec 17 00:01:26 cobalt3 kernel: ide3: reset: success
Dec 17 00:01:26 cobalt3 kernel: hdg: write_intr error1: nr_sectors=1, stat=0xd0
Dec 17 00:01:26 cobalt3 kernel: hdg: write_intr: status=0xd0 { Busy }
Dec 17 00:01:27 cobalt3 kernel: ide3: reset: success
whateverthehell that means ...
<snip>
that's the way it isA little still not enough info, but I will take your word that in general it just does not work and is not stable.
Thanks for the heads up, I do appreciate it.Yes, there is already an escalation running. There is a very kind technician
I wonder if someone from Sun/Cobalt will care to comment, or remain
anonymous cowards. ;)
of Sun Cobalt EMEA support in Netherlands who helped me a lot.
Yours
Jan*
_______________________________________________
cobalt-developers mailing list
[EMAIL PROTECTED]
http://list.cobalt.com/mailman/listinfo/cobalt-developers