Bascule;
Check the settings in /etc/sysconfig/network. I've found differences in
that file that will produce what you're seeing.
Mine is set:
HOSTNAME=aurora
DOMAIN=mlb.esid.northgrum.com
As such the hostname commands produce:
$> hostname
aurora
$> hostname -f
aurora.mlb.esid.northgrum.com
$> h
On Mon, Jan 20, 2003 at 07:18:04PM +, bascule wrote:
> default is obtained from gethostname() and as far as i can see that does
> indeed give the full name for this box, yet postfix wasn't having any of it!
>
You should set it like #hostname your-fqdn
and then postfix works. It's probably a m
further to this i've dicovered something interesting:
on the box that was upgraded to 9.0 hostname works like this:
$ hostname
sigerson.excession
$ hostname -f
sigerson.excession
$ hostname -d
excession
but on the clean 9.0 install it works like this:
$ hostname
mycroft
$ hostname -f
mycroft.exces
Am Montag, 20. Januar 2003 07:28 schrieb bascule:
>
>
> so, what have i forgotten, it's clear that
> #hostname -f gives the required result but i still get:
> [root@mycroft bascule]# mail bascule
> Subject: test
> Cc: Null message body; hope that's ok
> [root@mycroft bascule]# send-mail: warning: M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bascule wrote on Mon, Jan 20, 2003 at 07:18:04PM + :
> hi todd,
> when i checked /var/spool/postfix/etc/hosts was a copy of /etc/hosts
> explicitly specifiying it in main.cf worked, in fact expliclty specifying
> anything in main.cf works as i si
hi todd,
when i checked /var/spool/postfix/etc/hosts was a copy of /etc/hosts
explicitly specifiying it in main.cf worked, in fact expliclty specifying
anything in main.cf works as i simply uncommented out the examples they had
there, what bothers me is what was bothering praedor last year, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bascule wrote on Mon, Jan 20, 2003 at 06:28:57AM + :
> and
> HOSTNAME="mycroft"
> DOMAINNAME=excession
> in /etc/sysconfig/network due to ambiguity in the previous thread, also:
> [root@mycroft bascule]# cat /etc/hosts
> 127.0.0.1 lo
recognise this subject?
poor praedor had a whole saga with this last year and now i have the same
situation, i have just read the whole archived thread and i can say the
following:
[root@mycroft bascule]# hostname
mycroft
[root@mycroft bascule]# hostname -d
excession
[root@mycroft bascule]# host
On Tuesday 25 June 2002 12:41 pm, daRcmaTTeR wrote:
> On Tue, 25 Jun 2002, Praedor Tempus wrote:
> > BAH! Reinstalling MDK 8.2 again, this time trying a different fs
> > - third reinstall. First tried ext3 for first time. SLOW! Then
> > tried XFS. Good, quick, but then the problems related ab
On Tue, 25 Jun 2002, Praedor Tempus wrote:
> Manpage, schmanpage. I use them when possible but then there are those bogus
> pages that give the wrong command syntax (outdated or based on a non-linux
> system) or list the commands without providing for an example. To me, it
> doesn't count as
Praedor Tempus wrote on Tue, Jun 25, 2002 at 10:13:11AM -0500 :
>
> So, given this, the /etc/hosts is cool then (other than the duplicate
> 127.0.0.1 entry)?
Yes, it looks fine. :)
Blue skies... Todd
--
Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/
UNIX was not d
On Monday 24 June 2002 09:50 pm, Todd Lyons wrote:
> Praedor Tempus wrote on Mon, Jun 24, 2002 at 03:49:25PM -0500 :
> > /etc/hosts:
> > 127.0.0.1 localhost.localdomain localhost
>
> good start
>
> > 127.0.0.1 lapdog.ravenhome.netlapdog
>
> bad. Delete it.
>
> > 10.0.0.1
Manpage, schmanpage. I use them when possible but then there are those bogus
pages that give the wrong command syntax (outdated or based on a non-linux
system) or list the commands without providing for an example. To me, it
doesn't count as an example if the manpage begins with a command fol
On Mon, 2002-06-24 at 23:21, Todd Lyons wrote:
> After digging through the documentation available to me I have concluded
> that there is no technical basis for my conclusion that it was bad, just
> because it was a duplicate of the line above it.
>
> However, be careful about quoting out of cont
Praedor Tempus wrote:
> On Monday 24 June 2002 01:36 pm, civileme wrote:
>
>>Praedor Tempus wrote:
>>
>>>I am also a little leery of using linuxconf for this. It (linuxconf)
>>>appeared to bork my attempts at wlan ad-hoc networking and I was told not
>>>to use it in a wlan mailing list. In the
Mike Rambo wrote:
> daRcmaTTeR wrote:
>
>>
>>Mike,
>>
>>apart from sheery confusion your point in that post was...what?
>>
>>--
>>On Mon, 24 Jun 2002, Mike Rambo wrote:
>>
>>
>>>Praedor Tempus wrote:
>>>
I am also a little leery of using linuxconf for this. It (linuxconf) appeared
to bor
Dave Sherman wrote on Mon, Jun 24, 2002 at 10:32:04PM -0500 :
> > >
> > > /etc/hosts:
> > > 127.0.0.1 localhost.localdomain localhost
> > good start
> > > 127.0.0.1 lapdog.ravenhome.netlapdog
> > bad. Delete it.
> Out of curiosity, why is it "bad" to have two lines with differe
On Mon, 2002-06-24 at 21:50, Todd Lyons wrote:
> Praedor Tempus wrote on Mon, Jun 24, 2002 at 03:49:25PM -0500 :
> >
> > /etc/hosts:
> > 127.0.0.1 localhost.localdomain localhost
> good start
>
> > 127.0.0.1 lapdog.ravenhome.netlapdog
> bad. Delete it.
Out of curiosity, why i
Simon Naish wrote on Tue, Jun 25, 2002 at 12:47:57AM +0100 :
> At Last
> This:-
> > >Where are you changing the hostname (what file)? The
> > >hostname is set in /etc/sysconfig/network. /etc/hosts
> > >relates hostnames to IP addresses but doesn't really set
> > >anything.
> this is what isn't
Praedor Tempus wrote on Mon, Jun 24, 2002 at 03:49:25PM -0500 :
>
> /etc/hosts:
> 127.0.0.1 localhost.localdomain localhost
good start
> 127.0.0.1 lapdog.ravenhome.netlapdog
bad. Delete it.
> 10.0.0.1lapdog.ravenhome.netlapdog
good
> 10.0.0.5overlord.rave
Mike Rambo wrote:
>
>
> My answer included the following which was itself part of an
> earlier question Praedor asked. DrJung (I think - I've
> already deleted the mail so I can't be sure) expressed the
> idea that questions were being answered by folks on the list
> but that Praedor might be mi
ast
piece[s] in the puzzle would appear, and they did... /etc/sysconfig/network
...of course I've got to find something else busted to fix now ;-)
Si
- Original Message -
From: Mike Rambo <[EMAIL PROTECTED]>
Date: Mon, 24 Jun 2002 11:13:43 -0400
To: [EMAIL PROTECTED]
Su
On Monday 24 June 2002 01:36 pm, civileme wrote:
> Praedor Tempus wrote:
> >I am also a little leery of using linuxconf for this. It (linuxconf)
> > appeared to bork my attempts at wlan ad-hoc networking and I was told not
> > to use it in a wlan mailing list. In the past I have tried changing t
daRcmaTTeR wrote:
>
>
> Mike,
>
> apart from sheery confusion your point in that post was...what?
>
> --
> On Mon, 24 Jun 2002, Mike Rambo wrote:
>
> > Praedor Tempus wrote:
> > >
> > > I am also a little leery of using linuxconf for this. It (linuxconf) appeared
> > > to bork my attempts at
Praedor Tempus wrote:
>Thanks to you and daRmaTTeR.
>
>New question...at every bootup, my modem is "destroyed" by the system. I have
>a winmodem that works with a linmodem driver. The win/linmodem is
>/dev/tts/LT0 and is symlinked to /dev/modem. Upon bootup/reboot, this is
>destroyed and re
Praedor Tempus wrote:
>I am also a little leery of using linuxconf for this. It (linuxconf) appeared
>to bork my attempts at wlan ad-hoc networking and I was told not to use it in
>a wlan mailing list. In the past I have tried changing the hostname via
>linuxconf with mucked up results. I w
Praedor Tempus wrote on Mon, Jun 24, 2002 at 08:08:34AM -0500 :
> New question...at every bootup, my modem is "destroyed" by the system. I have
> a winmodem that works with a linmodem driver. The win/linmodem is
> /dev/tts/LT0 and is symlinked to /dev/modem. Upon bootup/reboot, this is
> des
On Mon, 24 Jun 2002, Mike Rambo wrote:
> Praedor Tempus wrote:
> >
> > I am also a little leery of using linuxconf for this. It (linuxconf) appeared
> > to bork my attempts at wlan ad-hoc networking and I was told not to use it in
> > a wlan mailing list. In the past I have tried changing the
Praedor Tempus wrote:
>
> I am also a little leery of using linuxconf for this. It (linuxconf) appeared
> to bork my attempts at wlan ad-hoc networking and I was told not to use it in
> a wlan mailing list. In the past I have tried changing the hostname via
> linuxconf with mucked up results.
On Mon, 24 Jun 2002, Praedor Tempus wrote:
> Thanks to you and daRmaTTeR.
>
> New question...at every bootup, my modem is "destroyed" by the system. I have
> a winmodem that works with a linmodem driver. The win/linmodem is
> /dev/tts/LT0 and is symlinked to /dev/modem. Upon bootup/reboot,
Thanks to you and daRmaTTeR.
New question...at every bootup, my modem is "destroyed" by the system. I have
a winmodem that works with a linmodem driver. The win/linmodem is
/dev/tts/LT0 and is symlinked to /dev/modem. Upon bootup/reboot, this is
destroyed and replaced with /dev/modem -> /de
On Mon, 24 Jun 2002, Praedor Tempus wrote:
> I am also a little leery of using linuxconf for this. It (linuxconf) appeared
> to bork my attempts at wlan ad-hoc networking and I was told not to use it in
> a wlan mailing list. In the past I have tried changing the hostname via
> linuxconf wit
I am also a little leery of using linuxconf for this. It (linuxconf) appeared
to bork my attempts at wlan ad-hoc networking and I was told not to use it in
a wlan mailing list. In the past I have tried changing the hostname via
linuxconf with mucked up results. I will give it a shot again bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd Lyons wrote:
| daRcmaTTeR wrote on Sun, Jun 23, 2002 at 09:16:58PM -0400 :
|
|>It's really quite simple. Open Linuxconf->Networking->Host name and IP
|
|
| I usually recommend not to use linuxconf except as a last resort. It
| does some things t
daRcmaTTeR wrote on Sun, Jun 23, 2002 at 09:16:58PM -0400 :
>
> It's really quite simple. Open Linuxconf->Networking->Host name and IP
I usually recommend not to use linuxconf except as a last resort. It
does some things to the system in a not friendly way and has left a bad
taste in my mouth.
Praedor Tempus wrote:
> OK, I want to change the name of my laptop from the default
> localhost.localdomain to lapdog.ravenhome.net. Looking at the manpage for
> hostname, it mentions: /etc/init.d/boot, /etc/hostname, and
> /etc/rc.d/rc.inet1 as where/how hostname is set. Uh-uh! Does not doe
sinip___
> EASY way is
>
> (gad, looks like that manpage wasn't written for SysVInit)
>
> Civileme
sanap_
Civilme
I checked it's identical to a FreeBSD2.2.8 box I have access to.. and
that's definitely not SysVinit.
James
On Sun, 23 Jun 2002 14:36:00 -0700
Todd Lyons <[EMAIL PROTECTED]> said with temporary authority
> Praedor Tempus wrote on Sun, Jun 23, 2002 at 04:18:14PM -0500 :
> > OK, I want to change the name of my laptop from the default
> > localhost.localdomain to lapdog.ravenhome.net. Looking at the
> >
On Sun, 23 Jun 2002 17:19:33 -0400
daRcmaTTeR <[EMAIL PROTECTED]> said with temporary authority
> James wrote:
> > On Sun, 23 Jun 2002 15:23:15 -0500
> > "J. Craig Woods" <[EMAIL PROTECTED]> said with temporary
> > authority
> >
> >
> >>daRcmaTTeR wrote:
> >>
> >>>J. Craig Woods wrote:
> >>>
>
Praedor Tempus wrote:
>OK, I want to change the name of my laptop from the default
>localhost.localdomain to lapdog.ravenhome.net. Looking at the manpage for
>hostname, it mentions: /etc/init.d/boot, /etc/hostname, and
>/etc/rc.d/rc.inet1 as where/how hostname is set. Uh-uh! Does not does n
Todd Lyons wrote:
>
> Praedor Tempus wrote on Sun, Jun 23, 2002 at 04:18:14PM -0500 :
> > OK, I want to change the name of my laptop from the default
> > localhost.localdomain to lapdog.ravenhome.net. Looking at the manpage for
> > hostname, it mentions: /etc/init.d/boot, /etc/hostname, and
> >
Praedor Tempus wrote on Sun, Jun 23, 2002 at 04:18:14PM -0500 :
> OK, I want to change the name of my laptop from the default
> localhost.localdomain to lapdog.ravenhome.net. Looking at the manpage for
> hostname, it mentions: /etc/init.d/boot, /etc/hostname, and
> /etc/rc.d/rc.inet1 as where/
OK, I want to change the name of my laptop from the default
localhost.localdomain to lapdog.ravenhome.net. Looking at the manpage for
hostname, it mentions: /etc/init.d/boot, /etc/hostname, and
/etc/rc.d/rc.inet1 as where/how hostname is set. Uh-uh! Does not does not!
There exists no /etc/
James wrote:
> On Sun, 23 Jun 2002 15:23:15 -0500
> "J. Craig Woods" <[EMAIL PROTECTED]> said with temporary authority
>
>
>>daRcmaTTeR wrote:
>>
>>>J. Craig Woods wrote:
>>>
Praedor, you need to help us understand why you can not complete
the simple task of naming a machine. Maybe you c
On Sun, 23 Jun 2002 15:23:15 -0500
"J. Craig Woods" <[EMAIL PROTECTED]> said with temporary authority
> daRcmaTTeR wrote:
> >
> > J. Craig Woods wrote:
> > >
> > > Praedor, you need to help us understand why you can not complete
> > > the simple task of naming a machine. Maybe you can send us so
daRcmaTTeR wrote:
>
> J. Craig Woods wrote:
> >
> > Praedor, you need to help us understand why you can not complete the
> > simple task of naming a machine. Maybe you can send us some log file
> > entries that give us specific errors messages...
> >
> > drjung
> >
>
> drjung,
>
> may he hasn't
J. Craig Woods wrote:
> civileme wrote:
>
>>OK, first of all you did not need to touch a wizard. Those are designed
>>for one-time setup which is why we call them wizards. They are not
>>tools to be used for maintenance, and they make a lot of assumptions, as
>>is appropriate for their target a
Somebody may have mentioned this earlier.
Postfix runs certain tasks chroot.
The jail is at /var/spool/postfix.
resolve.conf lives in /var/spool/postfix/etc
If resolve.conf is not set up when you install Postfix, this file will not be
correct.
I imagine HOSTNAME is passed through the envir
Praedor Tempus wrote:
>
> On Thursday 20 June 2002 07:26 am, Mike Rambo wrote:
> > Mike Rambo wrote:
> > > Praedor Tempus wrote:
> > > > On Wednesday 19 June 2002 12:03 pm, daRcmaTTeR wrote:
> > > > > Praedor Tempus wrote:
> > > > > > I am hesitant to try this again...I run postfix on my system a
49 matches
Mail list logo
