> Mark,
>
> I think someone already wrote to you that mon is causing the error
> messages? It's really only useful on a network AND if you trap its outputs
> to do something meaningful (like maybe page you?) IMO. If you want to use
> mon, you'd have to configure it to only let you know about services you
> care about because it's set to check something like every minute or two on
> some services by default. Those messages are a pleasure when you're vi'ing
> in console mode, lemme tell ya. :)))
>
> As for the Canon.... I have a BJC-600 and it printed fine until the
> magenta nozzle on the print head clogged up. But I'm not using cups at
> all; I just opted for lpr. I never did much of anything too fancy on it,
> just simple color output (I have a laser for pure black text). Have you
> tried getting rid of cups and just using lpr?
>
> Holly
Heavens! I didn't realize that when they responded that "mon" was an actual
program causing the ruckus. I guess I need to unplug for a bit. I'll have to
check into this and see if I can convince Mon to shut up and settle down.
And, I know what you mean about working in a console and the silly bugger
chirping at you. Really makes a mess of things. Just butts right in without
so much as a pardon me but did you know...?
Anoying little creature, but prolly one of those programs ya wouldn't want to
be without.
--
Mark
"If you don't share your concepts and ideals, they end up being worthless,"
"Sharing is what makes them powerful."
Linus Torvalds
