> Please can anyone tell me what might have sparked the message:
> lpr: unable to get official name for local machine
Sorry folks, I have found how I caused this - it was by deleting
a line
n.n.n.n bay
from /etc/hosts. ( I got the lpr source to find that out, I find if I put
the same IP n
Hi group:
Please can anyone tell me what might have sparked the message:
lpr: unable to get official name for local machine
I have re-installed the lpr from lpr_5.9-13.1.deb, but no cure that way.
hostname gets the right answer for the machine name (bay).
Root can cat to lp2 and print. /etc
Name resolving works again on my machines!
Still don't know what exactly happened though.
It seems that the reason for bind not working out of the 1.3-box for me,
is that I answered '' where I should have answered 'none' to
bindconfig (at least that is the only difference that I can think of.
Brian K Servis writes:
>
>For those of you following this here is an update.
>
>It appears to be some sort of name lookup failure. I can't figure it
>out. When I try and print with lpr it fails with the error given in
>the subject. This turns out is just an indicator of something else. I
>have a
On Fri, 6 Jun 1997, J.P.D. Kooij wrote:
:
:On Thu, 5 Jun 1997, Nathan E Norman wrote:
:
:> For what it's worth, I upgraded from 1.2 to 1.3 about a week ago on a
:> server that is authoritative for a few zones ... no problems at all.
:
:I forgot to mention the following: I let the install script c
On Thu, 5 Jun 1997, Nathan E Norman wrote:
> For what it's worth, I upgraded from 1.2 to 1.3 about a week ago on a
> server that is authoritative for a few zones ... no problems at all.
I forgot to mention the following: I let the install script change my
existing setup, did you do this too?
For what it's worth, I upgraded from 1.2 to 1.3 about a week ago on a
server that is authoritative for a few zones ... no problems at all.
I realise this doesn't assist you in solving your immediate problem, but
I'm not so sure that the Debian package is to blame..
--
Nathan Norman:Host
To me it looks like nameserving doesn't quite work out-of-the-box in
upcoming debian 1.3.
I've upgraded a box to frozen and that broke a working bind
configuration, I don't know how badly because I haven't really had the
time to look into it.
On fresh installations, nslookup can't find even l
For those of you following this here is an update.
It appears to be some sort of name lookup failure. I can't figure it
out. When I try and print with lpr it fails with the error given in
the subject. This turns out is just an indicator of something else. I
have a stand alone machine that I dia
Brian K Servis <[EMAIL PROTECTED]> writes:
[snip]
> WAIT A MINUTE..I just discovered something as I was checking the
> log files. ifconfig is making kerneld try to load some net-pf-4 and
> net-pf-5 module? What is this? I can't find any reference to it in
> the kernel-source.
>
> %root% da
Carey Evans writes:
>Brian K Servis <[EMAIL PROTECTED]> writes:
>
>[snip]
>
>> /etc/hosts:
>> 127.0.0.1 localhost loopback
>> widget-servis.ecn.purdue.edu
>> widget-servis
>> #(plus a bunch of other frequenctly used hosts at ecn.purdue.edu)
>
>[snip]
>
>> /etc/init.d/network:
Brian K Servis <[EMAIL PROTECTED]> writes:
[snip]
> /etc/hosts:
> 127.0.0.1 localhost loopback
> widget-servis.ecn.purdue.edu
> widget-servis
> #(plus a bunch of other frequenctly used hosts at ecn.purdue.edu)
[snip]
> /etc/init.d/network:
> ifconfig lo 127.0.0.1
> route
On Tue, 3 Jun 1997, Brian K Servis wrote:
> Jun 3 13:35:39 widget-servis lpd[374]: unable to get official name for local
> machine widget-servis
When my ISP drops my ppp connection I get the same thing. If I do a
hostname localhost
then printing works again.
Mark.
--
TO UNSUBSCRIBE
Jens B. Jorgensen writes:
>
>Brian K Servis wrote:
>>
>> Help!
>>
>> Ever since I upgrade to frozen(May 25) I am having all kinds of problems
>> with name resolution. Lpr is one of them, when lpd starts I get the
>> following repeated 5 times in messages:
>>
>> Jun 3 13:35:39 widget-servis lpd
Brian K Servis wrote:
>
> Help!
>
> Ever since I upgrade to frozen(May 25) I am having all kinds of problems
> with name resolution. Lpr is one of them, when lpd starts I get the
> following repeated 5 times in messages:
>
> Jun 3 13:35:39 widget-servis lpd[374]: unable to get official name fo
Help!
Ever since I upgrade to frozen(May 25) I am having all kinds of problems
with name resolution. Lpr is one of them, when lpd starts I get the
following repeated 5 times in messages:
Jun 3 13:35:39 widget-servis lpd[374]: unable to get official name for local
machine widget-servis
I conne
16 matches
Mail list logo
