On Thu 29 Mar 2018 at 23:05:06 (+0100), Brian wrote:
> On Thu 29 Mar 2018 at 18:34:42 +0000, Curt wrote:
> 
> > On 2018-03-29, mick crane <mick.cr...@gmail.com> wrote:
> > > following recent about hostname it seems I've been under 
> > > misunderstanding that ".local" was OK so now I change local domain to 
> > > ".home" .
> > > It's not just domainname and /etc/hosts. It's every frigging where.
> > > apache
> > > roundcube
> > > postfix
> > > now my ISP SMTP server is moaning.

Have you run
# dpkg-reconfigure exim4-config
yet? (Or equivalent for whatever's sending to it.)

> > > think I got them all except cups is unhappy, I don't know why.

Like exim, CUPS is more complicated as it works both ways. So it may
depend on whether you're running it as a server for a local printer
or a client for a networked printer. The latter has never caused me
any problem when changing the name of my domain. Howver, I haven't
done the former for about a decade, since my HP990 ran out of ink.
That might be more complicated, but I thought CUPS only needed
hostnames as it uses avahi (ie the "proper" use for .local).

> > There's actually a wiki on this:
> > 
> > https://wiki.debian.org/HowTo/ChangeHostname

I don't see the word "domain" on that page. But grepping for the
old name of the domain has never thrown up many references for me.
After all, software should be using getdomainname(), shouldn't it?

> > For cups you might look at 
> > 
> > /etc/printcap
> > 
> > the part after rm=
> >  rm=einstein
> >     ********
> 
> Whatever the OP's problem is (which he doesn't say) /etc/printcap will
> not solve it.
> 
> brian@desktop:~$ ls -l /etc/printcap
> lrwxrwxrwx 1 root root 22 Oct 13 13:31 /etc/printcap -> /var/run/cups/printcap
> 
> brian@desktop:~$ cat /etc/printcap | head -n 3
> # This file was automatically generated by cupsd(8) from the
> # /etc/cups/printers.conf file.  All changes to this file
> # will be lost.
> 
> https://debian-handbook.info/browse/stable/sect.config-printing.html
> 
> Bug#187954.

Yep, rebooting will recreate that file anyway, because /var/run is
just /run, and therefore ephemeral.

Cheers,
David.

Reply via email to