On Saturday 18 May 2019 08:50:07 am Dr. Nikolaus Klepp wrote: > Anno domini 2019 Sat, 18 May 08:46:33 -0400 > > Gene Heskett scripsit: > > On Saturday 18 May 2019 04:25:51 am Gene Heskett wrote: > > > On Saturday 18 May 2019 04:17:54 am Thierry de Coulon wrote: > > > > On Saturday 18 May 2019 10.00:36 Gene Heskett wrote: > > > > > My newly installed stretch/tde logs are being heavily spammed > > > > > by a task > > > > > > > > hpfax seems to be part of HPLIP. > > > > > > > > I find it here: usr/lib/cups/backend/hpfax > > > > > > > > You may try renaming it and, if hplip doen't protest, delete it. > > > > > > renamed it to hpfox, watching syslog. No squawks yet. We'll see > > > by daylight. > > > > > > Thanks. > > > > > > > Regards, > > > > > > > > Thierry > > > > Had this in the log when I woke for the day: > > May 18 01:08:36 coyote systemd[1]: cups.service: > > State 'stop-final-sigterm' timed out. Killing. > > May 18 01:08:36 coyote systemd[1]: cups.service: Killing process > > 1229 (hpfax) with signal SIGKILL. > > May 18 01:08:36 coyote systemd[1]: cups.service: Killing process > > 1236 (python) with signal SIGKILL. > > May 18 01:08:36 coyote systemd[1]: cups.service: Killing process > > 1253 (sh) with signal SIGKILL. > > May 18 01:08:36 coyote systemd[1]: cups.service: Killing process > > 1254 (hp) with signal SIGKILL. > > May 18 01:08:36 coyote systemd[1]: Stopped CUPS Scheduler. > > May 18 01:08:36 coyote systemd[1]: cups.service: Unit entered failed > > state. > > May 18 01:08:36 coyote systemd[1]: cups.service: Failed with > > result 'timeout'. > > May 18 01:08:36 coyote systemd[1]: Closed CUPS Scheduler. > > May 18 01:08:36 coyote systemd[1]: Stopping CUPS Scheduler. > > May 18 01:08:36 coyote systemd[1]: Listening on CUPS Scheduler. > > May 18 01:08:36 coyote systemd[1]: Stopped CUPS Scheduler. > > May 18 01:08:36 coyote systemd[1]: Stopping CUPS Scheduler. > > May 18 01:08:36 coyote systemd[1]: Started CUPS Scheduler. > > May 18 01:08:36 coyote systemd[1]: Started CUPS Scheduler. > > May 18 01:08:36 coyote systemd[1]: Started Make remote CUPS printers > > available locally. > > May 18 01:08:37 coyote colord[734]: failed to get session [pid > > 22342]: No such device or address > > May 18 01:08:37 coyote colord[734]: failed to get session [pid > > 22342]: No such device or address > > May 18 01:08:37 coyote colord[734]: failed to get session [pid > > 22342]: No such device or address > > > > Wierdsville. localhost:631 looks normal, everythings there. > > > > Now, pursuant to a log message, which showed me where cups keep its > > filters, I tried to add the missing filter using tde_print. /But it > > wouldn't let me do anything. It was asking for roots passwd, and > > root doesn't have one, I do everything of that nature with sudo, and > > if needed, su from there. It would not accept my pw for sudo. How > > do I fix this? Cups 2.21 itself has no provision in its > > configuration sequence to set a filter, one supplied by brother... > > Cups is a pita. Set a root password, that saves you a lot of trouble: > # sudo passwd root > cups is not a pita, it happily accepts the passwd of the admin user, which is me. Fix tde to accept sudo. > > > > ---------------------------------------------------------------- > > > >---- - To unsubscribe, e-mail: > > > > trinity-users-unsubscribe@... For > > > > additional commands, e-mail: > > > > trinity-users-help@... Read list messages > > > > on the web archive: > > > > http://trinity-users.pearsoncomputing.net/ Please remember not > > > > to top-post: > > > > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > > > > > > Cheers, Gene Heskett > > > > Cheers, Gene Heskett Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>