Re: repeat of previous question that has gone unansweredseveraltimes.

From	gene heskett <gheskett@shentel.net>
Newsgroups	linux.debian.user
Subject	Re: repeat of previous question that has gone unansweredseveraltimes.
Date	2023-05-10 19:20 +0200
Message-ID	<GtVDP-7Xda-1@gated-at.bofh.it> (permalink)
References	(6 earlier) <GttxT-7FVs-3@gated-at.bofh.it> <GtCrv-7Lbr-1@gated-at.bofh.it> <GtQXw-7Um9-1@gated-at.bofh.it> <GtSFX-7Vto-1@gated-at.bofh.it> <GtTVo-7W8I-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 5/10/23 11:29, Brian wrote:
> On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:
> 
>> On 5/10/23 08:17, Brian wrote:
> 
> [...]
> 
>>> Your nsswitch.conf line implies libnss-mymacines and libnss-mymhostname are used.
>>> They have man pages to help you decide what parts they play on bpi54.
>>
>> They were not installed, and neither are 95% of the manpages. man-db is
>> installed, pinfo is installed, neither has any knowledge of the missing man
>> pages.
> 
>    dpkg -L libnss-mymacines
>    man  nss-myhostname
> 
>>> What do you have on bpi51?
>>
>> bpi51 is busy, so bpi54 is being used, same iso installed both.
> 
> The same iso does not mean nsswitch.conf is the same on both. In fact, I think
> they are not identical.
>   
>> Man pages apparently are one of armbian's casualties. And avahi* and
>> cups-browsed has been reinstalled. When I went to bed last night, the
>> printers were being listed on the localhost:631/printers screen IF there is
>> an /etc/cups/client,conf containing the IP address:port of the shared
>> printers, but disappears if the machine name is used, And w/o manpages it
>> was not possible to find out that resolv.conf was using space separated
>> names and I had comma separated them. Fixed now.
> 
> Is /etc/cups/client,conf really, really needed?
> 
That is the first thing cups docs tell you to do, see "printer sharing"

>> Also on the bpi's, running armbian, libnss-ldap is installed, which
>> conflicts with installing libnss-*, but did install libnss-my*, and now the
>> printers have disappeared again.  That does not hold water. What the heck is
>> going on now?
> 
> I haven't any idea and do not claim the know anything about armbian and how
> it should deal with NSS\


Since that comes from a debian arm64 repo. my first assumption is that 
its identical.

>> doing a status request on the cups stuff shows that systemd restarted cups
>> and nearly everything else I just checked, a few seconds after midnight last
>> night, and now cups at localhost:631/printers is using a white cane again.
> 
> The scheduler restarts itself every 24 hours.
> 
Now, since my post earlier this morning, I restarted cups, no diff, Set 
reporting to debug, now getting 20k of noise in the error_log per 
disturbance. It claims that anytime it encounters the Server, this 
machine, that it cannot assign the address, but doesn't say why. Does 
that tell you anything. I will bump the debug to debug2 which logs 
everything. After lunch and a nap before I tackle a milling machine with 
a shorted home switch.

Take care & stay well.

  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, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Thread

repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 01:10 +0200
  Re: repeat of previous question that has gone unanswered several times. Lee <ler762@gmail.com> - 2023-05-01 02:20 +0200
    Re: repeat of previous question that has gone unanswered several  times. gene heskett <gheskett@shentel.net> - 2023-05-01 09:40 +0200
      Re: repeat of previous question that has gone unanswered several  times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
        Re: repeat of previous question that has gone unanswered  severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 15:50 +0200
          Re: repeat of previous question that has gone unanswered  severaltimes. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 16:10 +0200
            Re: repeat of previous question that has gone unanswered  severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:40 +0200
            Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
              Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:40 +0200
          Re: repeat of previous question that has gone unanswered  severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:20 +0200
            Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:10 +0200
              Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:20 +0200
              Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 18:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 19:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:00 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-02 01:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 20:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:10 +0200
                Re: repeat of previous question that has gone  unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-01 22:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 23:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
                Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:30 +0200
                Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
          Re: repeat of previous question that has gone unanswered severaltimes. Jeffrey Walton <noloader@gmail.com> - 2023-05-01 16:20 +0200
        Re: repeat of previous question that has gone unanswered  severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
  Re: repeat of previous question that has gone unanswered several  times. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 06:30 +0200
  Re: repeat of previous question that has gone unanswered several  times. john doe <johndoe65534@mail.com> - 2023-05-01 09:40 +0200
    Re: repeat of previous question that has gone unanswered several  times. <tomas@tuxteam.de> - 2023-05-01 13:50 +0200
      Re: repeat of previous question that has gone unanswered several  times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
        Re: repeat of previous question that has gone unanswered several  times. zithro <slack@rabbit.lu> - 2023-05-04 21:50 +0200
          Re: repeat of previous question that has gone unanswered  severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-04 22:00 +0200
            Re: repeat of previous question that has gone unanswered  severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 16:10 +0200
              Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 17:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 19:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 22:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-06 01:00 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-06 03:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Alex King <alex@king.net.nz> - 2023-05-07 01:30 +0200
                Re: repeat of previous question that has gone  unansweredseveraltimes. David <curmudgeon@telaman.net.au> - 2023-05-07 02:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Byung-Hee HWANG <soyeomul@doraji.xyz> - 2023-05-07 03:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 13:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-07 17:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-07 18:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 06:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-08 13:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 19:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 00:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 10:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-09 13:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 22:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 14:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 16:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. <tomas@tuxteam.de> - 2023-05-10 16:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 17:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 19:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 20:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:00 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:10 +0200
                Re: repeat of previous question that has gone  unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-10 22:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
                SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:10 +0200
                Re: SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 21:20 +0200
                Re: SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 00:00 +0200
                Re: SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 00:30 +0200
                Re: SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 01:50 +0200
                Re: SOLVED:Re: repeat of previous question that has  goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:40 +0200
                Re: SOLVED:Re: repeat of previous question that has  goneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 11:20 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 13:30 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
                Re: SOLVED:Re: repeat of previous question  thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:20 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
                :Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:10 +0200
                Re: :Re: repeat of previous question  thathasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 23:30 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-12 20:50 +0200
                Re: SOLVED:Re: repeat of previous question  thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 21:30 +0200
                Re: SOLVED:Re: repeat of previous question  thathasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-13 13:20 +0200
                Re: SOLVED:Re: repeat of previous  questionthathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-13 17:10 +0200
                Re: SOLVED:Re: repeat of previous question that has  goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:30 +0200
                Re: SOLVED:Re: repeat of previous question that has  goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 19:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 07:10 +0200

csiph-web