Date: Sun, 30 Mar 1997 12:42:17 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Michael Alwan <alwan@rma.edu> Cc: questions@freebsd.org Subject: Re: bad sysconfig affecting X and sendmail? Message-ID: <Pine.BSI.3.94.970330123624.242Q-100000@localhost> In-Reply-To: <333C96D6.41C67EA6@rma.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Mar 1997, Michael Alwan wrote: Wow, those quotes are ugly! Another strike against communicator. OK, line by line.. > > After installing 2.2.1 and all my packages from scratch, AND getting > user ppp running again :),(I destroyed 2.1.7 trying to upgrade) I have > of course created some new problems. Maybe someone can see it in the > dmesg output. One, turn line wrapping on. Try not writing your mail then file-importing it. > > cmd XF86_S3 pid 174 tried to use non-present SYSVSHM This is harmless. It means you need to rebuild your kernel and add options SYSVSHM to get full functionality, but it will still work fine. > ^^^^^^^ > The last line is something that pops up when I startx--if I > can startx. Found a mail message in the archives that said to give this > command as root: > > > > ifconfig lo0 up I will correct this below. > > 1) The X server problems mentioned above. No prob. > > 2) Syslogd bombs on boot with "syslogd: can't bind to host--child pid > 224 exited with return code 1. That isn't nice. > > 3) Sendmail (now disabled in sysconfig) hangs the boot process until I > hit cont rol-c: > > > > Mar 28 15:19:06 alwan sendmail[119]: My unqualified host name (alwan) > unknown; sleeping for retry This is a nameserver jam. Probably related to missing lo0. Modify /etc/hosts to add an entry for yourself and edit /etc/host.conf and put 'hosts' before 'bind'. > > Looking through some log messages, I found many mail messages about the alias.db being out of date: > > > > >Mar 28 06:40:11 207 sendmail[109]: alias database /etc/aliases.db out of date > > >Mar 28 07:03:22 207 sendmail[297]: alias database /etc/aliases.db out of date Run 'newaliases' as root. > > I thought I might as well drop my sysconfig file in this message--the answer may be right here. I think these lines from /etc/hosts are relevant too, since I guess that the hostname assignment in sysconfig reads something from hosts. As you can see, I'm set up for dynamic IP address assignment. When I installed 2.1.1 via ftp, I think it set my hostname in sysconfig as 207.0.141.1, which is one of the DNS's of my ISP. In any case, the first boot gave me messages about being unable to find host--seemed to be expecting a network connection. Maybe what really messed things up was changing my hostname to alwan (email address=alwan@rma.edu). > > > > 127.0.0.1 localhost > > 10.0.0.1 alwan alwan OK, I guess. > > ######################### Start Of Netconfig Section ####################### > > > > # Set to the name of your host - this is pretty important! > > hostname=alwan This should probably be a full name (ie alwan.isp.com) even if it doesn't really exist. If you do this add the name you add to /etc/hosts. 10.0.0.1 alwan alwan.isp.com > > # network_interfaces="ppp0 lo0" > > # ifconfig_ppp0="inet netmask 255.255.255.0" > > # ifconfig_ppp0="inet netmask 255.255.255.0" > > > > # ifconfig_lo0="inet 127.0.0.1" Why did you disable this? This is breaking everything. Fix to this: network_interfaces="lo0" ifconfig_lo0="inet 127.0.0.1" Reboot and it should work better. Hope this helps. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.970330123624.242Q-100000>