Re: Intel Macs and FreeBSD?
On Apr 27, 2006, at 1:52 PM, Bill Moran wrote: On Thu, 27 Apr 2006 15:47:37 -0500 James Riendeau [EMAIL PROTECTED] wrote: Why? Mac OS X has a complete unix freebsd-like core called darwin ( http://www.darwin.org ). There's no reason to install freebsd on it. Just install Mac Developer Tools (included in the Applications folder), compile your favorite progs and go. Have you actually tried this? Installing ports from FreeBSD is about 50x easier than getting software compiled/installed on a Mac. I've been working with the Macs here at the office for a few weeks, and I've come to realize just how wonderfully well-maintained FreeBSD's ports are! I'd take FreeBSD over MacOS any day. Perhaps it will get better over time, but I'm not impressed with it right now. At the risk of digressing on this topic, I want to add that I am actually at this point deciding between FreeBSD for the migration (i.e. 4.x on an old Gateway to 6.x on a Intel Mac Mini) and Ubuntu. The idea of moving to Ubuntu is that it might be simpler and less time-consuming to maintain a package-based system rather than building so much from source as I end up doing on FreeBSD. And that the fact it is a GUI-focused distribution might simplify things a bit (the idea being that Ubuntu has a very set design, less open-ended than FreeBSD, perhaps easier to upgrade?). The GUI might also help when others who are less unix-savvy than I have to or want to work with the server. I considered migrating to OSX on the mini, and I do maintain an OSX Server machine at work, but I don't like the lack of a port system. Everything has to be built and fitted in manually, and all monitoring of updates is also manual labor. Fink has its usefulness for desktop software, but the server packages are lacking. For the record, this server runs apache/php/mysql, exim, cyrus-imapd, proftpd, netatalk, samba, spamassassin, clamav, squirrelmail, mailman, and DNS. Stuff like that. It has about 20 users, it isn't super busy. So, how about it? Is the concept of running this off of Ubuntu being easier than FreeBSD just a pipe-dream? I have messed with Debian and Ubuntu, but never tried to run a server off of either. I would love to hear from people who have been down both roads, whether there is some sense to it, or if I should just stick with FreeBSD. Thanks for any insight, and thanks for the responses to this thread thus far... -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
cyrus-imapd 2.2.13 port failing to build
I am trying to upgrade to the cyrus-imapd 2.2.13 port. I have been running 2.2.12 successfully for many months. This is on FreeBSD 4.11p16. The build is failing as below. Does anyone have an idea if this is fixable? . . . cc -L/usr/lib -R/usr/lib -L/usr/local/lib -R/usr/local/lib -rpath=/ usr/lib:/usr/local/lib -o imapd ../master/service.o pushstats.o backend.o imapd.o index.o tls.o version.o mutex_fake.o libimap.a ../ lib/libcyrus.a ../lib/libcyrus_min.a -L/usr/local/lib -R/usr/local/ lib -lsasl2 -lfl -L/usr/local/lib -R/usr/local/lib -ldb41 -lssl - lcrypto -lmd ../et/libcom_err.a -lwrap ../lib/libcyrus.a(auth_krb5.o): In function `mycanonifyid': auth_krb5.o(.text+0x154): undefined reference to `krb5_init_context' auth_krb5.o(.text+0x16f): undefined reference to `krb5_parse_name' auth_krb5.o(.text+0x189): undefined reference to `krb5_get_default_realm' auth_krb5.o(.text+0x1c2): undefined reference to `krb5_build_principal' auth_krb5.o(.text+0x1d7): undefined reference to `krb5_free_principal' auth_krb5.o(.text+0x1e2): undefined reference to `krb5_free_context' auth_krb5.o(.text+0x209): undefined reference to `krb5_realm_compare' auth_krb5.o(.text+0x225): undefined reference to `krb5_free_principal' auth_krb5.o(.text+0x248): undefined reference to `krb5_unparse_name' auth_krb5.o(.text+0x25d): undefined reference to `krb5_free_principal' auth_krb5.o(.text+0x268): undefined reference to `krb5_free_context' auth_krb5.o(.text+0x29a): undefined reference to `krb5_free_principal' auth_krb5.o(.text+0x2a5): undefined reference to `krb5_free_context' *** Error code 1 Stop in /usr/ports/mail/cyrus-imapd22/work/cyrus-imapd-2.2.13/imap. *** Error code 1 Stop in /usr/ports/mail/cyrus-imapd22/work/cyrus-imapd-2.2.13. *** Error code 1 Stop in /usr/ports/mail/cyrus-imapd22. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Intel Macs and FreeBSD?
Does anyone know if the Intel Macs can boot and install FreeBSD, now that the firmware includes BIOS compatibility? Has anyone seen it happen? I'm thinking of using a Mac Mini as a quiet living-room server. Thanks! -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel Macs and FreeBSD?
Because I want to run FreeBSD, not Darwin. This is for a server, not for a desktop. I'm used to FreeBSD, and I am migrating an existing machine over. On Apr 27, 2006, at 1:49 PM, James Riendeau wrote: Oops. Looks like the URL changed. It is: http:// opensource.apple.com/ -james On Apr 27, 2006, at 3:47 PM, James Riendeau wrote: Why? Mac OS X has a complete unix freebsd-like core called darwin ( http://www.darwin.org ). There's no reason to install freebsd on it. Just install Mac Developer Tools (included in the Applications folder), compile your favorite progs and go. James Riendeau MMI Computer Support Technician 1300 University Ave Rm. 436, Dept. of MedMicro Madison, WI 53706 Phone: (608) 262-3351 After-hours Phone: (608) 260-2696 Fax: (608) 262-8418 Email: [EMAIL PROTECTED] On Apr 27, 2006, at 3:03 PM, Mark Edwards wrote: Does anyone know if the Intel Macs can boot and install FreeBSD, now that the firmware includes BIOS compatibility? Has anyone seen it happen? I'm thinking of using a Mac Mini as a quiet living-room server. Thanks! -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel Macs and FreeBSD?
The Mac Mini is fast, small, quiet, and cheap. Why is it not a good cheap server? On Apr 27, 2006, at 1:58 PM, John Cruz wrote: A mac mini is an odd machine to make into a server, but no matter. I doubt you'll run into any issues with installing it. Darwin is nice, but it was developed to be the underlying layer of the finder GUI. And the freeBSD ports system is so much nicer than any other nix install system that there's no comparison. -JOhn Mark Edwards wrote: Because I want to run FreeBSD, not Darwin. This is for a server, not for a desktop. I'm used to FreeBSD, and I am migrating an existing machine over. On Apr 27, 2006, at 1:49 PM, James Riendeau wrote: Oops. Looks like the URL changed. It is: http:// opensource.apple.com/ -james On Apr 27, 2006, at 3:47 PM, James Riendeau wrote: Why? Mac OS X has a complete unix freebsd-like core called darwin ( http://www.darwin.org ). There's no reason to install freebsd on it. Just install Mac Developer Tools (included in the Applications folder), compile your favorite progs and go. James Riendeau MMI Computer Support Technician 1300 University Ave Rm. 436, Dept. of MedMicro Madison, WI 53706 Phone: (608) 262-3351 After-hours Phone: (608) 260-2696 Fax: (608) 262-8418 Email: [EMAIL PROTECTED] On Apr 27, 2006, at 3:03 PM, Mark Edwards wrote: Does anyone know if the Intel Macs can boot and install FreeBSD, now that the firmware includes BIOS compatibility? Has anyone seen it happen? I'm thinking of using a Mac Mini as a quiet living-room server. Thanks! -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel Macs and FreeBSD?
On Apr 27, 2006, at 2:21 PM, Chad Leigh -- Shire.Net LLC wrote: On Apr 27, 2006, at 3:10 PM, Mark Edwards wrote: The Mac Mini is fast, small, quiet, and cheap. Why is it not a good cheap server? I would only be concerned about the disk depending on what sort of server you are intending to have. I do not know but assume that they still use the laptop 2.5 drives which are not 24/7 rated. Probably doesn't matter for most home servers. Lack of storage space unless you start hooking up external drives. What sort of server are you intending? I am actually thinking about using Mac Mini machines for IMAP and SMTP front ends using NFS mounted backend storage due to their size and low power draw. I can stick many of them in the same place that a 2U rack unit would go and with fans blowing data center A/C air across them there should be no heat issues and with the backend NFS storage, all the actual mail itself would be processed off-disk so the disks would basically get no work out... Fair points, and granted its not exactly a robust powerhouse machine. But certainly enough for a non-critical web/mail server. The internal drive is definitely a potential weak link. Its indeed a 2.5 Seagate laptop drive. That brings up an important point. I would want to hook up a USB2.0 or Firewire hard drive to the machine, either as a boot drive, a backup drive, or both (two drives). How is FreeBSD's support for USB or Firewire? Can one boot from these connections? Is it reliable enough for server use? In any case, this is a significant upgrade from my current box, which is a Gateway Pentium Pro 180Mhz tower with 128MB of RAM and two IDE internal drives, running FreeBSD 4.11. Why such a box? Its relatively quiet, and it was free (from the garbage even). Its been running my web/mail for 4 years with almost no downtime though... :-) -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel Macs and FreeBSD?
On Apr 27, 2006, at 4:45 PM, Dan Busarow wrote: On Apr 27, 2006, at 4:59 PM, Mark Edwards wrote: On Apr 27, 2006, at 2:21 PM, Chad Leigh -- Shire.Net LLC wrote: That brings up an important point. I would want to hook up a USB2.0 or Firewire hard drive to the machine, either as a boot drive, a backup drive, or both (two drives). How is FreeBSD's support for USB or Firewire? Can one boot from these connections? Is it reliable enough for server use? We've got a FreeBSD 5.x NFS/Samba/AppleTalk file server at work using Lacie firewire drives (purchased at the local Mac store in keeping with the thread) Works great. Just replaced one of the drives that was starting to report errors during rsync. Drive was about 2 years old. The other drives are still going strong. Dan Does it boot from Firewire, or is that just for storage? Is the machine a Mac? An Intel Mac? Thanks! -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: verrevpath -- ipfw: unknown argument ``not''
On Nov 26, 2005, at 7:18 AM, Lowell Gilbert wrote: Mark Edwards [EMAIL PROTECTED] writes: I am trying to implement the verrevpath suggestion in the ipfw man page, as follows: The verrevpath option could be used to do automated anti- spoofing by adding the following to the top of a ruleset: ipfw add deny ip from any to any not verrevpath in However, when I try to add the rule, I get an error: lilbuddy:~ paimin$ ipfw add deny ip from any to any not verrevpath in ipfw: unknown argument ``not'' Can someone tell what is causing this syntax to fail? Thanks! Works fine for me right now on -STABLE (RELENG_6). You didn't mention what you were running, so there's not much else we can tell you. Sorry, I am running 4.11, and nothing weird that I know of that would affect ipfw operation. I found a posting via google from someone with the same question, and then he replied to himself that reading the man page had given him the answer, but he didn't say what that answer was. Tried to email him, but it bounced because my mail gateway doesn't have an SPF record so his server rejected my mail (even though my server DOES have an SPF record -- ugh). Thanks! -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
verrevpath -- ipfw: unknown argument ``not''
I am trying to implement the verrevpath suggestion in the ipfw man page, as follows: The verrevpath option could be used to do automated anti- spoofing by adding the following to the top of a ruleset: ipfw add deny ip from any to any not verrevpath in However, when I try to add the rule, I get an error: lilbuddy:~ paimin$ ipfw add deny ip from any to any not verrevpath in ipfw: unknown argument ``not'' Can someone tell what is causing this syntax to fail? Thanks! -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Perl / Webmin: ld-elf.so.1 issue
On Oct 3, 2005, at 4:20 PM, Lowell Gilbert wrote:
Mark Edwards [EMAIL PROTECTED] writes:
On Oct 3, 2005, at 1:33 AM, Lowell Gilbert wrote:
Mark Edwards [EMAIL PROTECTED] writes:
I am getting the following error in the browser when trying to use
webmin's crontab editing feature:
/usr/libexec/ld-elf.so.1: /usr/local/bin/perl: Undefined symbol
PL_exit_flags
crontab: /usr/local/lib/webmin/cron/cron_editor.pl exited with
status 1
I am running perl 5.8.7 from ports, and I have done the whole
routine
with setting use.perl port and perl_after_upgrade.
I notice that there are two /usr/libexec/ld-elf.so.1 files on my
machine:
-r-xr-xr-x 1 root wheel85940 Feb 11 2005 ld-elf.so.1
-r-xr-xr-x 1 root wheel85908 Jun 29 2004 ld-elf.so.1.old
Is that normal? I reinstalled the perl port to no avail.
Are your ports up to date?
[From an up-to-date ports tree?]
Yes, up to date from cvs as of a week ago or so. Can anyone suggest
a way for me to troubleshoot what exactly the problem is?
Well, that symbol is definitely supposed to be present in your perl
executable.
[E.g.,
[ strings /usr/local/bin/perl|grep exit_fl
[ PL_exit_flags
[
Do you have any perl-related knobs in make.conf, or in pkgtools.conf
(if you used portupgrade for installing)?
Well, I get the same result when I run the above command. I suspect
that it isn't perl itself that is the problem, but rather another
port or an issue with my system.
One thing I wonder is about how I did my last system upgrade. I did
it long-distance, and so was unable to boot into single-user mode, so
I just shut everything down and did the make installworld live, and
then rebooted. I wonder if something wasn't done correctly then,
although I didn't get any complaints from the process, that I was
aware of.
The other possibility is that this is a problem with webmin, although
that doesn't seem likely since this error seems to indicate something
broken with perl. Still, why is this the only place where the error
is showing up? Lots of other stuff uses perl on my machine -- exim,
spam-assassin, etc.
My /etc/make.conf is pretty simple:
lilbuddy:/usr/src paimin$ cat /etc/make.conf
CFLAGS= -O -pipe
NOPROFILE= true# Avoid compiling profiled libraries
MAKE_IDEA= YES # IDEA (128 bit symmetric encryption)
USA_RESIDENT= YES
#WITH_GTK=yes
WITH_OPENSSL_BASE=yes
# port settings
.if ${.CURDIR:M*/mail/exim}
WITH_AUTH_SASL=yes
.endif
# added by use.perl 2005-09-30 16:58:27
PERL_VER=5.8.7
PERL_VERSION=5.8.7
NOPERL=yes
--
Mark Edwards
[EMAIL PROTECTED]
cell: +46704070332
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Perl / Webmin: ld-elf.so.1 issue
On Oct 3, 2005, at 1:33 AM, Lowell Gilbert wrote: Mark Edwards [EMAIL PROTECTED] writes: I am getting the following error in the browser when trying to use webmin's crontab editing feature: /usr/libexec/ld-elf.so.1: /usr/local/bin/perl: Undefined symbol PL_exit_flags crontab: /usr/local/lib/webmin/cron/cron_editor.pl exited with status 1 I am running perl 5.8.7 from ports, and I have done the whole routine with setting use.perl port and perl_after_upgrade. I notice that there are two /usr/libexec/ld-elf.so.1 files on my machine: -r-xr-xr-x 1 root wheel85940 Feb 11 2005 ld-elf.so.1 -r-xr-xr-x 1 root wheel85908 Jun 29 2004 ld-elf.so.1.old Is that normal? I reinstalled the perl port to no avail. Are your ports up to date? [From an up-to-date ports tree?] Yes, up to date from cvs as of a week ago or so. Can anyone suggest a way for me to troubleshoot what exactly the problem is? -- Mark Edwards [EMAIL PROTECTED] cell: +46704070332 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Perl / Webmin: ld-elf.so.1 issue
I am getting the following error in the browser when trying to use webmin's crontab editing feature: /usr/libexec/ld-elf.so.1: /usr/local/bin/perl: Undefined symbol PL_exit_flags crontab: /usr/local/lib/webmin/cron/cron_editor.pl exited with status 1 I am running perl 5.8.7 from ports, and I have done the whole routine with setting use.perl port and perl_after_upgrade. I notice that there are two /usr/libexec/ld-elf.so.1 files on my machine: -r-xr-xr-x 1 root wheel85940 Feb 11 2005 ld-elf.so.1 -r-xr-xr-x 1 root wheel85908 Jun 29 2004 ld-elf.so.1.old Is that normal? I reinstalled the perl port to no avail. -- Mark Edwards [EMAIL PROTECTED] cell: +46704070332 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openssl 0.9.8 breaking things
On Sep 28, 2005, at 7:26 PM, Gary Kline wrote: On Wed, Sep 28, 2005 at 06:48:03PM +0200, Daniel Gerzo wrote: Hello Mark, Wednesday, September 28, 2005, 6:41:47 PM, you contributed this to our collective wisdom: Just upgraded to openssl 0.9.8 and things are breaking, namely exim and cyrus-imap. Non-SSL connections work, SSL connections cause a segfault. I'm going back to 0.9.7g using the WITH_OPENSSL_097 flag, but is there some way to make this work with 0.9.8? Have I totally missed something here? you need to recompile your software (exim,cyrus-imap,...) against new openssl libs. I'll toss in my two cents here just FWIW. I had troubles with all sorts of sh* (stuff) breaking when I touched openssl. I had not---or maybe I did, inadvertently--used the openssl port. I *had* to use /usr/src/secure/openssl/whatever; when applications began breaking. I pkg_deleted openssl and rebuilt the native /usr/src/* stuff. These apps are tightly interdependent; that's why you are seeing things break. This may or may not work generally. It cost me at least a day's investigation ... and I'm *still* not sure that everything's right. I think I have a clue as to why this is becoming complicated. I didn't have either WITH_OPENSSL_BASE=yes or WITH_OPENSSL_PORT=yes in / etc/make.conf. What must be happening is that some things are using the base openssl, and some are using the port, which is causing a conflict. That's my guess. For whatever reason, the 0.9.7g port doesn't cause a conflict, whereas 0.9.8 does. I don't really see the point of having the openssl port installed, in my case. Its only installed because some port wanted it and built it, and I didn't have WITH_OPENSSL_BASE=yes set. So, I'm now going to set WITH_OPENSSL_BASE=yes, remove the openssl port, and rebuild everything that depended upon the openssl port. Can anyone either refute any of the above guesses, or tell me why I am a fool to go with the base openssl rather than the port? Thanks! -- Mark Edwards [EMAIL PROTECTED] cell: +46704070332 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
openssl 0.9.8 breaking things
Just upgraded to openssl 0.9.8 and things are breaking, namely exim and cyrus-imap. Non-SSL connections work, SSL connections cause a segfault. I'm going back to 0.9.7g using the WITH_OPENSSL_097 flag, but is there some way to make this work with 0.9.8? Have I totally missed something here? This is FreeBSD 4.11. Thanks! -- Mark Edwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openssl 0.9.8 breaking things
On Sep 28, 2005, at 6:48 PM, Daniel Gerzo wrote: Hello Mark, Wednesday, September 28, 2005, 6:41:47 PM, you contributed this to our collective wisdom: Just upgraded to openssl 0.9.8 and things are breaking, namely exim and cyrus-imap. Non-SSL connections work, SSL connections cause a segfault. I'm going back to 0.9.7g using the WITH_OPENSSL_097 flag, but is there some way to make this work with 0.9.8? Have I totally missed something here? you need to recompile your software (exim,cyrus-imap,...) against new openssl libs. Thanks, I'm getting it under control now. I tried recompiling things at first, but I missed a component, which made it seem like there was just an incompatibility. Its slowly coming back to life now... -- Mark Edwards [EMAIL PROTECTED] cell: +46704070332 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openssl 0.9.8 breaking things
On Sep 28, 2005, at 7:26 PM, Gary Kline wrote: On Wed, Sep 28, 2005 at 06:48:03PM +0200, Daniel Gerzo wrote: Hello Mark, Wednesday, September 28, 2005, 6:41:47 PM, you contributed this to our collective wisdom: Just upgraded to openssl 0.9.8 and things are breaking, namely exim and cyrus-imap. Non-SSL connections work, SSL connections cause a segfault. I'm going back to 0.9.7g using the WITH_OPENSSL_097 flag, but is there some way to make this work with 0.9.8? Have I totally missed something here? you need to recompile your software (exim,cyrus-imap,...) against new openssl libs. This is FreeBSD 4.11. Thanks! I'll toss in my two cents here just FWIW. I had troubles with all sorts of sh* (stuff) breaking when I touched openssl. I had not---or maybe I did, inadvertently--used the openssl port. I *had* to use /usr/src/secure/openssl/whatever; when applications began breaking. I pkg_deleted openssl and rebuilt the native /usr/src/* stuff. These apps are tightly interdependent; that's why you are seeing things break. This may or may not work generally. It cost me at least a day's investigation ... and I'm *still* not sure that everything's right. gary I take back what I said about things working. I was fooled into thinking things were working when I had deinstalled 0.9.8 and things started working again. I reinstalled 0.9.8 and things broke again, with no other changes. Now I'm reinstalling 0.9.7g and hoping for the best. I guess I have to install 0.9.8 and clean install everything that depends on it, at a time when I can have everything broken for several hours. Just rebuilding cyrus-imap, cyrus-sasl, and exim didn't do it. -- Mark Edwards [EMAIL PROTECTED] cell: +46704070332 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
arplookup 192.168.1.254 failed: host is not on local network
I've just put my server on a new connection that requires DHCP, even for a fixed IP. Anyway, the DHCP server gives a fixed public internet IP to my server, but it communicates on 192.168.1.254, which angers FreeBSD (4.11). I get a lot of the following: arplookup 192.168.1.254 failed: host is not on local network Which makes sense, because as far as FreeBSD is concerned, interface ep1 is on the internet not on a LAN. Looking on the net, I found the following suggestion, which does cure the errors: /sbin/route add -net 192.168.1.254 -netmask 255.255.255.0 -interface 1 My question is, is that the proper way to deal with this? I have to issue this statement whenever the dhclient is restarted. I've currently placed it in my firewall script, but is there a proper or more elegant way to achieve this? Thanks! -- Mark Edwards [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: arplookup 192.168.1.254 failed: host is not on local network
On Mar 1, 2005, at 11:21 AM, Lowell Gilbert wrote: Mark Edwards [EMAIL PROTECTED] writes: I've just put my server on a new connection that requires DHCP, even for a fixed IP. Anyway, the DHCP server gives a fixed public internet IP to my server, but it communicates on 192.168.1.254, which angers FreeBSD (4.11). I get a lot of the following: arplookup 192.168.1.254 failed: host is not on local network Which makes sense, because as far as FreeBSD is concerned, interface ep1 is on the internet not on a LAN. Exactly. Looking on the net, I found the following suggestion, which does cure the errors: /sbin/route add -net 192.168.1.254 -netmask 255.255.255.0 -interface 1 My question is, is that the proper way to deal with this? It's not bad. I would use -host instead of -net and -netmask, and it will fail if the DHCP server ever changes its address, but what you are doing is is working and fairly likely to stay that way. How would you phrase the command? I just tried -host and couldn't get it to work. I have to issue this statement whenever the dhclient is restarted. I've currently placed it in my firewall script, but is there a proper or more elegant way to achieve this? If you want something more elegant, you could specify a script for one of the dhclient-script(8) hooks, and put the route in there. You would be able to refer to the interface and server address by variables which dhclient-script provides... Great! I put the command in /etc/dhclient-exit-hooks and it works great on a reboot. I don't really see which variables I can use in the dhclient-script man page though. Do you know which variables would do this? Thanks! -- Mark Edwards [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: arplookup 192.168.1.254 failed: host is not on local network
On Mar 1, 2005, at 12:53 PM, Lowell Gilbert wrote: Looking on the net, I found the following suggestion, which does cure the errors: /sbin/route add -net 192.168.1.254 -netmask 255.255.255.0 -interface 1 My question is, is that the proper way to deal with this? It's not bad. I would use -host instead of -net and -netmask, and it will fail if the DHCP server ever changes its address, but what you are doing is is working and fairly likely to stay that way. How would you phrase the command? I just tried -host and couldn't get it to work. e.g., route add -host 172.10.212.2 -interface bge0 I tried that syntax and I get errors like this: Mar 1 13:12:37 lilbuddy /kernel: arp: 00:0d:72:d7:d9:a1 attempts to modify permanent entry for 192.168.1.254 on ep1 If I use the -net -netmask syntax I don't get the errors. -- Mark Edwards [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: swap getting consumed
On Jan 23, 2005, at 7:27 PM, J65nko BSD wrote: On Sun, 23 Jan 2005 17:33:35 -0800, Mark Edwards [EMAIL PROTECTED] wrote: On Jan 23, 2005, at 3:48 PM, J65nko BSD wrote: On Sun, 23 Jan 2005 14:53:38 -0800, Mark Edwards [EMAIL PROTECTED] wrote: I have posted about this problem a couple of times with not much response, I'm afraid, but here is a different take on it perhaps. I have a 4.10p5 running and for roughly the last two months my swap space has been getting eaten uncontrollably. The only clue I have is that it resets when I restart Apache (1.3.33), and so if I set up a cron job to restart Apache every day or hour the problem is contained: https://secure.antsclimbtree.com/mrtg/ants.swap-year.png Oddly, my physical memory doesn't seem to be generally affected: https://secure.antsclimbtree.com/mrtg/ants.ram-year.png I have 128MB of physical RAM and 384MB of swap. The only clue I have with Apache is a lot of this in /var/log/messages: Jan 21 18:25:06 lilbuddy /kernel: pid 68446 (httpd), uid 80: exited on signal 6 But I'm not sure what to make of it. The only thing Google turns up related to those messages are notes about CodeRed virus attacks, but Apache 1.3.33 is suppose to address that issue. Does anyone have any suggestion of how to attack this problem? I'm totally stumped. You don't give much background info about the server. Which modules Apache is using, mod_perl, mod_ssl?, which applications it runs, WebMail? Cannot you see in the Apache logs, which pages are being served before the time of the signal 6 messages? Google for Apache+memory+leak and include every module or app you are running.. Gather more info what the system is doing exactly. Write a script for cron to run netstat -m, sockstat -4, ps -ax. at regular times and have the output mailed to you. BTW 128 MB memory for a webserver is not much these days ;) =Adriaan= Thanks for the reply. I am running apache+mod_ssl-1.3.33+2.8.22, with mod_php4 and mod_dav. As far as web apps, I run Squirrelmail, phpbb2, MT-2.661, Mailman, analog, webalizer. The weird thing is that I ran all of those except phpbb2 for years with no problem. Perhaps it is phpbb2's doing, but I can't find a correlation between that and the signal 6 messages, and in any case phpbb2 hardly gets used. I can watch swap go up and up without anyone actually using phpbb2. Doing Google on Apache+memory+leak as you suggest leads to people describing similar situations, where Apache eats more and more swap and has to be restarted, but I can't find anyone posing a solution to the problem. I will just keep monitoring it I guess, looking for clues. 128MB might not be much, but it has worked fine for running essentially the same set of software for years, and all of a sudden there's a problem. I wish I could tie it to some specific update or change, but I can't. The closest I can come is turning on softupdates and installing phpbb2, and neither of those seems to correlate. Very odd... Have you seen this security warning for phpbb? http://www.auscert.org.au/render.html?it=4653 Just want to close this thread by saying that I seem to have solved the problem, although I'm not 100% sure what did it. I'm pretty sure it was a recompile of mm-1.3.1. I tried this because I noticed that it was the only required component for apache that was last updated in mid-November, right around when this nonsense started. All the other required ports had been updated more recently, so I figured that perhaps something was amiss when that one got compiled in November. Plus, the fact that mm deals with memory management. That appears to have been the culprit. I'm running along with swap moving between the 100MB and 200MB range, with no big spikes, and RAM at a steady 64MB out of 128MB. Performance is steady and back to normal. Hurrah! A 180Mhz Pentium Pro with 128MB RAM is no speed demon, mind you, but it serves web pages, hosts email, and routes pretty damn fine for a machine that was literally in the garbage when I rescued it. PHP is a bit slow, but still totally acceptable, and faster than the 256Kbps outgoing connection. I also doubled my swap from 400MB on one drive to 800MB between two drives. And I stripped down my kernel a bit, removing lots of options that aren't used on this box. Those might have affected things as well, but my hunch is it was mm-1.3.1 that was out of whack. Anyway, all's well that ends well. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
swap getting consumed
I have posted about this problem a couple of times with not much response, I'm afraid, but here is a different take on it perhaps. I have a 4.10p5 running and for roughly the last two months my swap space has been getting eaten uncontrollably. The only clue I have is that it resets when I restart Apache (1.3.33), and so if I set up a cron job to restart Apache every day or hour the problem is contained: https://secure.antsclimbtree.com/mrtg/ants.swap-year.png Oddly, my physical memory doesn't seem to be generally affected: https://secure.antsclimbtree.com/mrtg/ants.ram-year.png I have 128MB of physical RAM and 384MB of swap. The only clue I have with Apache is a lot of this in /var/log/messages: Jan 21 18:25:06 lilbuddy /kernel: pid 68446 (httpd), uid 80: exited on signal 6 But I'm not sure what to make of it. The only thing Google turns up related to those messages are notes about CodeRed virus attacks, but Apache 1.3.33 is suppose to address that issue. Does anyone have any suggestion of how to attack this problem? I'm totally stumped. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Memory issues on 4.10 server
I'm having two weird memory issues that have cropped up on my 4.10 server: 1) Apache runs away and creates tons of processes and eventually takes down the server, eating up tons of processes. I see regular notifications like the following: Jan 6 07:25:09 lilbuddy /kernel: pid 16828 (httpd), uid 80: exited on signal 6 I've taken to restarting Apache once an hour, which has curtailed the problem for now. But I would love to figure out why this is happening and so far have not been able to find many clues. The only Apache-related thing that has changed in the last several months is adding phpbb to the server. 2) snmpd also has had some freakouts where it eats up more and more swap space until it no longer functions. Restarting snmpd clears the problem. I'm using snmpd in conjunction with MRTG. This phenomenon does not seem to take down the server, surprisingly. It still functions relatively responsively. This doesn't happen regularly and I haven't seen it in a few days so I don't see a pattern yet. It is perhaps related to the Apache problem. Its hard to say, because when Apache freaks out, it starts to take the server down and that affects all sorts of things. Obviously I'm not onto the source of these issues, because my efforts to identify that have so far been in vain. Anyone who can give me some advice would be much appreciated. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Runaway Apache
In the last week or so, my FreeBSD 4.10p5 server has started locking up every day or so, to the point where it becomes unusable and must be rebooted to resume service. I've noticed that when it happens, the following type of thing appears in /var/log/httpd-error.log [Sat Dec 18 13:00:18 2004] [error] child process 248 still did not exit, sending a SIGKILL [Sat Dec 18 13:00:18 2004] [error] child process 464 still did not exit, sending a SIGKILL [Sat Dec 18 13:00:18 2004] [error] child process 465 still did not exit, sending a SIGKILL [Sat Dec 18 13:00:18 2004] [error] child process 466 still did not exit, sending a SIGKILL [Sat Dec 18 13:00:18 2004] [error] child process 554 still did not exit, sending a SIGKILL [Sat Dec 18 13:00:18 2004] [error] child process 2121 still did not exit, sending a SIGKILL [Sat Dec 18 13:00:18 2004] [error] child process 2126 still did not exit, sending a SIGKILL [Sat Dec 18 13:00:18 2004] [error] child process 2129 still did not exit, sending a SIGKILL [Sat Dec 18 13:00:18 2004] [error] child process 2130 still did not exit, sending a SIGKILL and on and on and on... So, apparently, Apache is having a problem and taking down the server. I eventually also see complaints about user 80 exceeding the kern.maxfiles limit. That's probably when the server really takes a dump. I've been monitoring top periodically to see if I can spot the problem, and an httpd process was consuming 95% of the cpu just now, and sure enough the above messages were streaming through the log. I also notice the following: httpd in free(): warning: chunk is already free httpd in free(): warning: chunk is already free httpd in free(): warning: chunk is already free httpd in free(): warning: chunk is already free httpd in free(): warning: chunk is already free httpd in free(): warning: chunk is already free httpd in free(): warning: chunk is already free Now, my problem is I'm not sure how to find the source of this problem and stop it. A google search on those log entries suggests that it may be an attempt to exploit the Chunk Handling Vulnerability, but my Apache is newer than the fix for that. http://httpd.apache.org/info/security_bulletin_20020617.txt Anyhow, can anyone give me a suggestion on how to troubleshoot this? Thanks! Here is the Apache in question: Server Version: Apache/1.3.33 (Unix) mod_ssl/2.8.22 OpenSSL/0.9.7e PHP/4.3.10 DAV/1.0.3 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Deleting /usr/X11R6 and /etc/X11
On Oct 8, 2004, at 11:37 AM, Toomas Aas wrote: Hi! I decided to remove XFree86 from my server since I don't really use it and its just taking up space. So I removed all gui ports, including all of gnome and XFree86. Done. Now, I'm wondering if there is any reason I shouldn't just delete /usr/X11R6 and /etc/X11? Aren't they just taking up space? Are those directories part of the a base FreeBSD 4.x install? These directories seem to exist on all my 4.x servers where I've never explicitly installed XFree86 or any other X system. So it's probably safer to not touch them. (/etc/X11 is empty on my machines, though). Thanks for the comments. I have since discovered that in fact some server packages, such as ImageMagick, in fact need XFree86-libraries-4 which uses /usr/X11R6. So I just cleaned that directory of gnome as best I could, re-installed XFree86-libraries-4, and I'm leaving it at that. /etc/X11 is empty now, except for my XF86Config which I will leave there to save me the hassle of reconfiguring if I ever decide to re-enable XFree86. Thanks for the help! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Deleting /usr/X11R6 and /etc/X11
I decided to remove XFree86 from my server since I don't really use it and its just taking up space. So I removed all gui ports, including all of gnome and XFree86. Done. Now, I'm wondering if there is any reason I shouldn't just delete /usr/X11R6 and /etc/X11? Aren't they just taking up space? Are those directories part of the a base FreeBSD 4.x install? Are there other X11-related directories that I could wipe as well? Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND 8.3 going insane on FreeBSD 4.9
Well, I have any query allowed on my domains, and tcp/udp port 53 is open to all from any port. Is there anything else necessary to allow root queries? I generally don't have this problem; its only happened twice in 4 years, so it doesn't seem like a configuration issue on my end. I host public DNS for 10 domains. Will setting BIND to forward only really make any difference in this case? Does BIND still have to communicate with the root servers when dealing with its own domains? Does anyone know exactly what's causing this problem? Is it out-of-date root hints, or what? There seems to be some opinion on the net that this is a BIND 8 bug. On Jan 29, 2004, at 10:18 PM, Richard van Vliet wrote: Be sure that jou server can recieve query's directly from the rootservers, it happend at my place when the firewall blocked these rootname server query's. I had the same problem logs filling up in minutes... Configure your private BIND server to use forwarders only, it wil then query itself for its one zones and the forwarder for any other. Regards Richard. -Oorspronkelijk bericht- Van: Mark Edwards [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 30 januari 2004 2:17 Aan: [EMAIL PROTECTED] Onderwerp: BIND 8.3 going insane on FreeBSD 4.9 So, I've seen this twice now. BIND completely flips its lid and utterly destroys the server. Logs say: 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs found for root NS (D.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (A.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (H.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (C.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (G.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (F.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (B.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (J.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (M.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (I.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (L.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (D.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (A.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (H.ROOT-SERVERS.NET) My root hints are up to date, and I've seen this both using forwarders and not. I've read that this is some incompatibility between BIND 8.3 and other servers. Is the only solution to this problem to run BIND 9? I really have to make sure this doesn't happen again, because it has catastrophic effects on the server. Thanks for any help! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
BIND 8.3 going insane on FreeBSD 4.9
So, I've seen this twice now. BIND completely flips its lid and utterly destroys the server. Logs say: 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs found for root NS (D.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (A.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (H.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (C.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (G.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (F.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (B.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (J.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (M.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (I.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (L.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (D.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (A.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (H.ROOT-SERVERS.NET) My root hints are up to date, and I've seen this both using forwarders and not. I've read that this is some incompatibility between BIND 8.3 and other servers. Is the only solution to this problem to run BIND 9? I really have to make sure this doesn't happen again, because it has catastrophic effects on the server. Thanks for any help! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RELENG CVS syncronization question
I was just syncing my /usr/src using cvs to get today's security updates to 4.8, and I noticed that if I use cvsup3.FreeBSD.org I get one version of the files, which appears to be 4.8p5. But, if I use cvsup4.FreeBSD.org I get a different versions of the files, which appears to be 4.8p8, which is what I want. My questions is, how do I know I've actually got 4.8p8? The only way I know to check is to read /usr/src/UPDATING, but how do I know I've got all the right files? Can I assume that if UPDATING says its a particular version, then my source is indeed current with that version? Thanks... -- Mark Edwards ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql323-server -- can't connect remotely
Okay, I figured it out. It had absolutely nothing to do with user permissions. It was, amazingly, tcpwrappers that was causing the problem. I discovered a ton of log entries like the following in my Security Output email: Mar 7 00:22:11 lilbuddy inetd[968]: refused connection from 192.168.1.1, service auth (tcp) I edited /etc/hosts.allow and uncommented ALL : ALL : allow from the top of it. Sure enough, mysql connections with a -h specified started working! Now, I couldn't quite figure out why connections where being stopped. The log entries seem to indicate it has something to do with auth, but here's the auth line from my /etc/hosts.allow: auth : ALL : allow I decided to add the following to /etc/hosts.allow: mysqld: ALL : allow That did it. It works fine now. Apparently this is normal, as I've now found some websites that mention needing to tweak /etc/hosts.allow for mysqld. I'm amazed that this isn't in the mysql manual though. Ridiculous. Perhaps this is fairly new? On Friday, March 7, 2003, at 03:18 PM, [EMAIL PROTECTED] wrote: http://www.mysql.com/doc/en/Adding_users.html I have /usr/ports/databases/mysql323-server installed, and it is up and running. If I do: mysql -h localhost Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 3.23.55 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql It works fine. However, if I do: mysql -h lilbuddy.antsclimbtree.com ERROR 2013: Lost connection to MySQL server during query Do you have an entry for 'lilbuddy.antsclimbtree.com' in the user and db tables in your mysql database? That's what I get. lilbuddy.antsclimbtree.com is the hostname of the server machine, and I'm doing this from that machine. Any idea what's wrong? Thanks! -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
mysql323-server -- can't connect remotely
I have /usr/ports/databases/mysql323-server installed, and it is up and running. If I do: mysql -h localhost Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 3.23.55 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql It works fine. However, if I do: mysql -h lilbuddy.antsclimbtree.com ERROR 2013: Lost connection to MySQL server during query That's what I get. lilbuddy.antsclimbtree.com is the hostname of the server machine, and I'm doing this from that machine. Any idea what's wrong? Thanks! -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mysql323-server -- can't connect remotely
On Friday, March 7, 2003, at 02:34 PM, Kjell wrote: I have /usr/ports/databases/mysql323-server installed, and it is up and running. If I do: mysql -h localhost Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 3.23.55 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql It works fine. However, if I do: mysql -h lilbuddy.antsclimbtree.com ERROR 2013: Lost connection to MySQL server during query Do you have an entry for 'lilbuddy.antsclimbtree.com' in the user and db tables in your mysql database? Yes, the test database and the anonymous user are accessible from any host. In any case, I believe the error would be ERROR 1130: Host 'lilbuddy.antsclimbtree.com' is not allowed to connect to this MySQL server if that was the problem. -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mysql323-server -- can't connect remotely
I issued the necessary GRANT statements to add a new user, as described on that page, and I get: mysql -u marktest -p -h antsclimbtree.com Enter password: ERROR 2013: Lost connection to MySQL server during query Same thing. Again, shouldn't the error message be different if this is a permissions problem? On Friday, March 7, 2003, at 03:18 PM, [EMAIL PROTECTED] wrote: http://www.mysql.com/doc/en/Adding_users.html I have /usr/ports/databases/mysql323-server installed, and it is up and running. If I do: mysql -h localhost Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 3.23.55 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql It works fine. However, if I do: mysql -h lilbuddy.antsclimbtree.com ERROR 2013: Lost connection to MySQL server during query Do you have an entry for 'lilbuddy.antsclimbtree.com' in the user and db tables in your mysql database? That's what I get. lilbuddy.antsclimbtree.com is the hostname of the server machine, and I'm doing this from that machine. Any idea what's wrong? Thanks! -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Monitor standby + gnome 2.2 and XFree86-4.2.0
I upgraded from Gnome 1.x and XFree86-3.x to Gnome 2.2 and XFree86-4.2.0 (latest versions of ports) and monitor-standby with xscreensaver stopped working. Under the previous setup, I could set a time for the monitor to go into standby mode, and it would. Now, I set the time, but it never goes into standby. xscreensaver works otherwise, just no standby. I did a google search and saw references to a bug involving DPMS in a Redhat forum, but I didn't quite understand it. Anyone have any suggestions to get it working, or where I might inquire or look? Thanks! -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Friday, February 14, 2003, at 11:21 AM, stan wrote: On Thu, Feb 13, 2003 at 11:46:47AM -0800, Mark Edwards wrote: On Thursday, February 13, 2003, at 11:29 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-13 at 13:03, Mark Edwards wrote: I've fixed my XFree86 install, and I have 4.2.1 running. All of the ports mentioned above are installed. I am able to run xf86cfg graphically and configure, and I can run X using startx, which loads fine. However, when I do: sudo /usr/X11R6/etc/rc.d/gdm.sh start I get: Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display server several times in a short time period; disabling display :0 I would need to see the X log to know if it's a gdm problem. However, I've never tried starting gdm under sudo. Well, the same behavior occurs if I just restart the machine and let the script be triggered normally, so I doubt that sudo has anything to do with it. Also, I successfully started gdm many times this way under gnome 2.0. I have posted /var/log/:0.log and var/log/XFree86.0.log here: http://mark.antsclimbtree.com/Xlog.txt Nothing useful here. You might try doing a forced rebuild of gdm2. Joe I got it. I tried switching to root, and running startx (root's .xinitrc was set to start gnome). I got a complaint that fontconfig couldn't start. Aha! I removed /usr/X11R6/etc/fonts and reinstalled /usr/ports/x11-fonts/fontconfig and voila! Everything's fine, AND I have anti-aliased fonts! Damn, that was painful, but I guess it was worth it. Im fighting this exact same problem, and I was wondering if I could trouble you with a couple of questions. You say you removed /usr/X11R6/etc/fonts. Do you mean the whole thing? As in evert font on the system? If so, exactly what did you do to reinstall just the fonts? My /usr/X11R6/etc/fonts directory looks like this: total 16 -r--r--r-- 1 root wheel 8618 Feb 13 11:35 fonts.conf -r--r--r-- 1 root wheel 5712 Feb 13 11:35 fonts.dtd So, I removed that directory, and I did cd /usr/ports/x11-fonts/fontconfig make deinstall make clean install That fixed the problem for me. I don't know that deleting the fonts.conf and fonts.dtd actually did anything, I was just shooting in the dark. I saw that something was foul with fontconfig, so I wanted to make sure I wiped out anything corrupted in fonts.conf. I knew the installer would replace that directory. If two of us have had this issue now, I wonder if there's something about the build order of the gnome2.2 port that is messing up fontconfig when upgrading from a previous gnome2 install, or something like that. Does that sound plausible Joe? -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tuesday, February 11, 2003, at 02:30 PM, Scott A. Moberly wrote: My two cents in here real quick, what does: pkg_info | fgrep XFree86 give? pkg_info | fgrep XFree86 XFree86-libraries-4.2.1_6 XFree86-4 include/(shared) library kit imake-4.2.0_1 Imake and other utilities from XFree86 First of all you probably need to install: XFree86-fontDefaultBitmaps-4.2.0 XFree86-4 default bitmap fonts to deal with the explicit problem on your X startup. Though this may not work as you also want the following packages: XFree86-Server-4.2.1_7 XFree86-4 X server and related programs XFree86-clients-4.2.1_2 XFree86-4 Client environments XFree86-font100dpi-4.2.0 XFree86-4 bitmap 100 dpi fonts XFree86-font75dpi-4.2.0 XFree86-4 bitmap 75 dpi fonts XFree86-fontEncodings-4.2.0 XFree86-4 font encoding files XFree86-fontScalable-4.2.0 XFree86-4 Scalable font files wrapper-1.0_2 Wrapper for XFree86-4 server freetype2-2.1.3_1 A free and portable TrueType font rendering engine Some aren't strictly necessary, but... If you are in a rush you could install these one by one (starting with default fonts) until you are up and running otherwise make install clean deinstall everything you 'think' you have and start from scratch. Okay, well I've made some progress, but still can't get gdm/gnome running with 2.2. I've fixed my XFree86 install, and I have 4.2.1 running. All of the ports mentioned above are installed. I am able to run xf86cfg graphically and configure, and I can run X using startx, which loads fine. However, when I do: sudo /usr/X11R6/etc/rc.d/gdm.sh start I get: Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display server several times in a short time period; disabling display :0 So, my problems seem to be specifically with gnome 2.2. I was running gnome 2.0 with no problems before doing a portupgrade -ra and getting the new gnome 2.2 stuff installed. I did have a fairly goofy XFree86 install, granted, but it ran. In any case, my /var/log/:0.log and /var/log/XFree86.0.log show no errors. gdm just isn't starting up. Where can I look for clues? I've tried installing /usr/ports/x11/gnome2 again just to make sure nothing is missing, but it says everything is found. Perhaps I should cvs and portupgrade? I'm stuck... -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 13, 2003, at 08:52 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-13 at 04:42, Mark Edwards wrote: On Tuesday, February 11, 2003, at 02:30 PM, Scott A. Moberly wrote: My two cents in here real quick, what does: pkg_info | fgrep XFree86 give? pkg_info | fgrep XFree86 XFree86-libraries-4.2.1_6 XFree86-4 include/(shared) library kit imake-4.2.0_1 Imake and other utilities from XFree86 First of all you probably need to install: XFree86-fontDefaultBitmaps-4.2.0 XFree86-4 default bitmap fonts to deal with the explicit problem on your X startup. Though this may not work as you also want the following packages: XFree86-Server-4.2.1_7 XFree86-4 X server and related programs XFree86-clients-4.2.1_2 XFree86-4 Client environments XFree86-font100dpi-4.2.0 XFree86-4 bitmap 100 dpi fonts XFree86-font75dpi-4.2.0 XFree86-4 bitmap 75 dpi fonts XFree86-fontEncodings-4.2.0 XFree86-4 font encoding files XFree86-fontScalable-4.2.0 XFree86-4 Scalable font files wrapper-1.0_2 Wrapper for XFree86-4 server freetype2-2.1.3_1 A free and portable TrueType font rendering engine Some aren't strictly necessary, but... If you are in a rush you could install these one by one (starting with default fonts) until you are up and running otherwise make install clean deinstall everything you 'think' you have and start from scratch. Okay, well I've made some progress, but still can't get gdm/gnome running with 2.2. I've fixed my XFree86 install, and I have 4.2.1 running. All of the ports mentioned above are installed. I am able to run xf86cfg graphically and configure, and I can run X using startx, which loads fine. However, when I do: sudo /usr/X11R6/etc/rc.d/gdm.sh start I get: Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display server several times in a short time period; disabling display :0 I would need to see the X log to know if it's a gdm problem. However, I've never tried starting gdm under sudo. Well, the same behavior occurs if I just restart the machine and let the script be triggered normally, so I doubt that sudo has anything to do with it. Also, I successfully started gdm many times this way under gnome 2.0. I have posted /var/log/:0.log and var/log/XFree86.0.log here: http://mark.antsclimbtree.com/Xlog.txt Thanks. -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 13, 2003, at 11:29 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-13 at 13:03, Mark Edwards wrote: I've fixed my XFree86 install, and I have 4.2.1 running. All of the ports mentioned above are installed. I am able to run xf86cfg graphically and configure, and I can run X using startx, which loads fine. However, when I do: sudo /usr/X11R6/etc/rc.d/gdm.sh start I get: Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display server several times in a short time period; disabling display :0 I would need to see the X log to know if it's a gdm problem. However, I've never tried starting gdm under sudo. Well, the same behavior occurs if I just restart the machine and let the script be triggered normally, so I doubt that sudo has anything to do with it. Also, I successfully started gdm many times this way under gnome 2.0. I have posted /var/log/:0.log and var/log/XFree86.0.log here: http://mark.antsclimbtree.com/Xlog.txt Nothing useful here. You might try doing a forced rebuild of gdm2. Joe I got it. I tried switching to root, and running startx (root's .xinitrc was set to start gnome). I got a complaint that fontconfig couldn't start. Aha! I removed /usr/X11R6/etc/fonts and reinstalled /usr/ports/x11-fonts/fontconfig and voila! Everything's fine, AND I have anti-aliased fonts! Damn, that was painful, but I guess it was worth it. I'm not sure what was fubar'd with fontconfig, but maybe make a mental note of it in case someone else is upgrading to gnome2.2 and gnome suddenly stops working. Could have simply been corruption on my end because of running a funky XFree86 3.3.6/gnome2 setup or something. I don't know and at this point I don't care, cause it works! Thanks for your patience, Joe... -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Friday, February 7, 2003, at 12:05 AM, Joe Marcus Clarke wrote: On Fri, 2003-02-07 at 02:58, Mark Edwards wrote: Well, I have the XFree86-libraries-4.2.1_6 port installed, and my XF86Config file contains: Section Module Load freetype Load type1 EndSection I think that fits the bill, but obviously something is wrong... Probably is the lack of RENDER support. Since it works for Mozilla, it should work for GNOME 2.2, so just be patient. I've just finished all the ports, and assuming I didn't miss anything in my documentation updates, I'll start the merge when I wake up tomorrow. Well, I updated to 2.2 today, and while I was still in the gnome desktop, it seemed to fix the anti-aliasing issues I was having. However, I restarted, and now I get this: Feb 11 00:51:32 lilbuddy gdm[24662]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:34 lilbuddy gdm[24666]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:39 lilbuddy gdm[24670]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:44 lilbuddy gdm[24674]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:44 lilbuddy gdm[24661]: Failed to start X server several times in a short time period; disabling display :0 I've seen this before, of course. gdm is starting from /usr/X11R6/etc/rc.d/gdm.sh, so that's not it. I removed the font-related alterations I made recently, that's not it. How do I figure out what's causing gdm to hang? -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tuesday, February 11, 2003, at 12:37 PM, Joe Marcus Clarke wrote: Well, I updated to 2.2 today, and while I was still in the gnome desktop, it seemed to fix the anti-aliasing issues I was having. However, I restarted, and now I get this: Feb 11 00:51:32 lilbuddy gdm[24662]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:34 lilbuddy gdm[24666]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:39 lilbuddy gdm[24670]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:44 lilbuddy gdm[24674]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:44 lilbuddy gdm[24661]: Failed to start X server several times in a short time period; disabling display :0 I've seen this before, of course. gdm is starting from /usr/X11R6/etc/rc.d/gdm.sh, so that's not it. I removed the font-related alterations I made recently, that's not it. How do I figure out what's causing gdm to hang? Not sure. What's in your /var/log/XFree86.0.log? Joe I think I'm onto it. I don't have a /var/log/XFree86.0.log, but I do have a /var/log/:0.log (where'd that name come from?), and it says: XFree86 Version 3.3.6 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: xx November 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: FreeBSD 4.5-PRERELEASE i386 [ELF] Configured drivers: Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 1) Using syscons driver with X support (version 2.0) (using VT number 9) XF86Config: /etc/XF86Config (**) stands for supplied, (--) stands for probed/default values (--) no ModulePath specified using default: /usr/X11R6/lib/modules freetype: Unknown error loading module type1: Unknown error loading module (**) XKB: rules: xfree86 (**) XKB: model: pc101 (**) XKB: layout: us (**) Mouse: type: SysMouse, device: /dev/mouse, resolution: 100 (**) Mouse: buttons: 3, 3 button emulation (timeout: 50ms) (**) Mach64: Graphics device ID: Primary Card (**) Mach64: Monitor ID: Primary Monitor Warning: 'fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/local. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/local). (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled, /usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/ X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/ fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/webfonts/ (--) Mach64: PCI: Mach64 CT rev 9, Aperture @ 0xfe00, Block I/O @ 0xfc00 (--) Mach64: Card type: PCI (--) Mach64: Memory type: DRAM (1) (--) Mach64: Clock type: Internal (--) Mach64: Maximum allowed dot-clock: 80.000 MHz (**) Mach64: Mode 800x600: mode clock = 60.750 (--) Mach64: Virtual resolution: 800x600 (--) Mach64: Video RAM: 2048k (--) Mach64: Using hardware cursor (--) Mach64: Using 16 MB aperture @ 0xfe00 (--) Mach64: Ramdac is Internal (--) Mach64: Ramdac speed: 80 MHz (**) Mach64: Color weight: 565 (--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 slots (--) Mach64: Font cache: 0 fonts failed to set default font path '/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled, /usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/ X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/ fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/webfonts/ ' Fatal server error: could not open default font 'fixed' When reporting a problem related to a server crash, please send the full server output, not just the last messages Now, I'd say the error is clear. Do I just need to run mkfontdir on my font directories? Odd that I need to do that, since this was a working installation before the 2.2 update. Other questions -- why does the log report XFree86 Version 3.3.6 on FreeBSD 4.5 PRERELEASE? As far as I can tell I'm running XFree86 4.2.1, and I'm definitely running FreeBSD 4.7p4. That's scary. Maybe I need to completely reinstall and reconfigure XFree86? Is that as simple as removing the XFree86-libraries-4.2.1_6 package and reinstalling it? Do I just need to go to /stand/sysinstall and re-configure XFree86? Very odd. -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tuesday, February 11, 2003, at 01:57 PM, Joe Marcus Clarke wrote: You may have accidentally overwritten X. However, it could also be that this file is very ancient, and doesn't properly reflect what's going on now. If you've found you've messed up X, you should remove all XFree86 packages, then reinstall the XFree86-4 meta-port. Joe I'm beginning to suspect my XFree86 install is toast. My man pages say 3.3.6. I think I had 3.3.6 installed from the original FreeBSD 4.3 or something like that, and somehow didn't fully remove it. When I do cd /usr/ports/x11/XFree86 sudo make deinstall it says the port isn't installed. However, I don't have XFree86-4 installed either, and my XFree86 man pages say 3.3.6, so clearly 3.3.6 didn't get deinstalled and is still half-working. Is there a way to say, deinstall the files that would be installed if this port was installed? Or, would it be best to install /usr/ports/x11/XFree86, and then deinstall it? I'm pretty sure if I can get 3.3.6 totally gone, and then install /usr/ports/x11/XFree86-4, I'm going to be set. Sorry to be bringing such a fubar'd system to you! -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tuesday, February 11, 2003, at 02:19 PM, Scott A. Moberly wrote: I'm beginning to suspect my XFree86 install is toast. My man pages say 3.3.6. I think I had 3.3.6 installed from the original FreeBSD 4.3 or something like that, and somehow didn't fully remove it. When I do cd /usr/ports/x11/XFree86 sudo make deinstall it says the port isn't installed. However, I don't have XFree86-4 installed either, and my XFree86 man pages say 3.3.6, so clearly 3.3.6 didn't get deinstalled and is still half-working. Is there a way to say, deinstall the files that would be installed if this port was installed? Not that I know of. Perhaps portupgrade and friends have this capability. Or, would it be best to install /usr/ports/x11/XFree86, and then deinstall it? This would do it, but you might be able to get away with just installing XFree86-4 over top your existing X disaster. Joe I'm pretty sure if I can get 3.3.6 totally gone, and then install /usr/ports/x11/XFree86-4, I'm going to be set. Sorry to be bringing such a fubar'd system to you! -- Mark Edwards Engineer Mr. Toad's San Francisco, CA -- PGP Key : http://www.marcuscom.com/pgp.asc My two cents in here real quick, what does: pkg_info | fgrep XFree86 give? pkg_info | fgrep XFree86 XFree86-libraries-4.2.1_6 XFree86-4 include/(shared) library kit imake-4.2.0_1 Imake and other utilities from XFree86 -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Friday, February 7, 2003, at 12:05 AM, Joe Marcus Clarke wrote: On Fri, 2003-02-07 at 02:58, Mark Edwards wrote: Well, I have the XFree86-libraries-4.2.1_6 port installed, and my XF86Config file contains: Section Module Load freetype Load type1 EndSection I think that fits the bill, but obviously something is wrong... Probably is the lack of RENDER support. Since it works for Mozilla, it should work for GNOME 2.2, so just be patient. I've just finished all the ports, and assuming I didn't miss anything in my documentation updates, I'll start the merge when I wake up tomorrow. Joe Great! Let me know if you need any other info from me... -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 6, 2003, at 09:27 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-06 at 12:14, Joe Marcus Clarke wrote: 2) gdm2 crashes if I go to the configure tool, close, then go to the configure tool again. I saw this same behavior in gdm, and it was solved by starting via /etc/ttys, I think. Is there anyway to fix this? Basically, once I go to the configure tool, I have to resart gdm2 if I want to go to the configure tool again. I haven't seen this, but I'll take a look. I've verified this does not happen in the GNOME 2.2 gdm2. Joe But you don't know if it does happen with 2.0, right? Its funny because I had the same issue with gdm a while back. I wonder if its due to something else on my machine. I guess I'll wait for 2.2 and see. Thanks. -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Gnome 2 on FreeBSD 4.7p3 -- multiple issues
1) Is there any way to run xscreensaver with gdm2? With gdm, there was a Background option in the config tool, but that's gone. 2) gdm2 crashes if I go to the configure tool, close, then go to the configure tool again. I saw this same behavior in gdm, and it was solved by starting via /etc/ttys, I think. Is there anyway to fix this? Basically, once I go to the configure tool, I have to resart gdm2 if I want to go to the configure tool again. 3) I followed the directions to get font anti-aliasing working, and I do have GDK_USE_XFT set to 1 via .gnomerc. However, I don't see any difference in anti-aliasing. There was some anti-aliasing before I did anything at all, for instance in mozilla some fonts are anti-aliased. But there is none in the gnome2 desktop even after the new settings. What am I missing? Do I just need to add the proper fonts or something? Thanks! -- Mark Edwards San Francisco, CA
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 6, 2003, at 09:14 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-06 at 12:07, Mark Edwards wrote: 1) Is there any way to run xscreensaver with gdm2? With gdm, there was a Background option in the config tool, but that's gone. What do you mean? Run xscreensaver while gdm itself is running (i.e. no user logged in)? I've never done this, but there are quite a few configuration options in the /usr/X11R6/etc/gdm/gdm.conf that are not in the GUI tool. Yes, I want the monitor to go into standby after 5 minutes of the login screen. 2) gdm2 crashes if I go to the configure tool, close, then go to the configure tool again. I saw this same behavior in gdm, and it was solved by starting via /etc/ttys, I think. Is there anyway to fix this? Basically, once I go to the configure tool, I have to resart gdm2 if I want to go to the configure tool again. I haven't seen this, but I'll take a look. 3) I followed the directions to get font anti-aliasing working, and I do have GDK_USE_XFT set to 1 via .gnomerc. However, I don't see any difference in anti-aliasing. There was some anti-aliasing before I did anything at all, for instance in mozilla some fonts are anti-aliased. But there is none in the gnome2 desktop even after the new settings. What am I missing? Do I just need to add the proper fonts or something? You need to make sure your XftConfig is setup correctly, and you have the latest freetype2. It hardly merits any work now as I'm on the verge of committing GNOME 2.2 which no longer requires GDK_USE_XFT. Ah. So if XftConfig is set up properly, I should see everything anti-aliased, is that right? -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 6, 2003, at 09:14 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-06 at 12:07, Mark Edwards wrote: 1) Is there any way to run xscreensaver with gdm2? With gdm, there was a Background option in the config tool, but that's gone. What do you mean? Run xscreensaver while gdm itself is running (i.e. no user logged in)? I've never done this, but there are quite a few configuration options in the /usr/X11R6/etc/gdm/gdm.conf that are not in the GUI tool. I figured this out. gdm2 has removed the BackgroundProgram feature from the configuration gui, but it still exists in gdm.conf. You have to set BackgroundProgram=/usr/X11R6/bin/xscreensaver -nosplash and also RunBackgroundProgramAlways=true However, it doesn't seem to work with the new graphical greeter. That's what got me. Use the default greeter, and set the above settings in gdm.conf (and put an .xscreensaver in the gdm home directory) and you get xscreensaver during the login window. 2) gdm2 crashes if I go to the configure tool, close, then go to the configure tool again. I saw this same behavior in gdm, and it was solved by starting via /etc/ttys, I think. Is there anyway to fix this? Basically, once I go to the configure tool, I have to resart gdm2 if I want to go to the configure tool again. I haven't seen this, but I'll take a look. I think I spoke too quickly on this one. It appears that on second load, the gdm configure tool just takes a really long time on my machine. I mistook this for the crashing that I saw with gdm under gnome 1.4, which I originally solved by a re-install. Sorry for the false alarm! 3) I followed the directions to get font anti-aliasing working, and I do have GDK_USE_XFT set to 1 via .gnomerc. However, I don't see any difference in anti-aliasing. There was some anti-aliasing before I did anything at all, for instance in mozilla some fonts are anti-aliased. But there is none in the gnome2 desktop even after the new settings. What am I missing? Do I just need to add the proper fonts or something? You need to make sure your XftConfig is setup correctly, and you have the latest freetype2. It hardly merits any work now as I'm on the verge of committing GNOME 2.2 which no longer requires GDK_USE_XFT. I've done a bit of work on this, despite your suggestion not to, and I'm still coming up short. I found a tutorial that suggests xdpyinfo | grep -c -i render as a test to see if XFree86 is including render support. Doing this on my system returns 0 instead 1 which the tutorial says is necessary for anti-aliasing. The tutorial says wait until XFree86 supports Render on your graphics card. This is an old machine with an ATI Mach64 CT, so I would believe it is unsupported, however ... What's strange is that anti-aliasing is clearly occurring in a few places for me, most notably in Mozilla. In Mozilla Mail, a message displayed in fixed-width font (Courier) is quite clearly anti-aliased, next to a variable-width font (Times) that is not. Zooming the text to 600% makes this quite evident. I also have seen anti-aliased text in the gdm2 graphic greeter. These two examples existed even before I had added GDK_USE_XFT to my environment, or followed any of the directions in the FAQ for enabling anti-aliased text. So, there is anti-aliasing going on without any settings whatsoever, but following the directions in the FAQ, adding all my font directories to XftConfig, and setting match edit antialias=true; in that file, still results in most fonts not being anti-aliased. Any thoughts on what is wrong? -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 6, 2003, at 11:53 PM, Joe Marcus Clarke wrote: 3) I followed the directions to get font anti-aliasing working, and I do have GDK_USE_XFT set to 1 via .gnomerc. However, I don't see any difference in anti-aliasing. There was some anti-aliasing before I did anything at all, for instance in mozilla some fonts are anti-aliased. But there is none in the gnome2 desktop even after the new settings. What am I missing? Do I just need to add the proper fonts or something? You need to make sure your XftConfig is setup correctly, and you have the latest freetype2. It hardly merits any work now as I'm on the verge of committing GNOME 2.2 which no longer requires GDK_USE_XFT. I've done a bit of work on this, despite your suggestion not to, and I'm still coming up short. I found a tutorial that suggests xdpyinfo | grep -c -i render as a test to see if XFree86 is including render support. Doing this on my system returns 0 instead 1 which the tutorial says is necessary for anti-aliasing. The tutorial says wait until XFree86 supports Render on your graphics card. This is an old machine with an ATI Mach64 CT, so I would believe it is unsupported, however ... What's strange is that anti-aliasing is clearly occurring in a few places for me, most notably in Mozilla. In Mozilla Mail, a message displayed in fixed-width font (Courier) is quite clearly anti-aliased, next to a variable-width font (Times) that is not. Zooming the text to 600% makes this quite evident. I also have seen anti-aliased text in the gdm2 graphic greeter. These two examples existed even before I had added GDK_USE_XFT to my environment, or followed any of the directions in the FAQ for enabling anti-aliased text. So, there is anti-aliasing going on without any settings whatsoever, but following the directions in the FAQ, adding all my font directories to XftConfig, and setting match edit antialias=true; in that file, still results in most fonts not being anti-aliased. Any thoughts on what is wrong? What version of X is this? You really need a recent 4.2.x version with freetpye and type1 modules loaded. Joe Well, I have the XFree86-libraries-4.2.1_6 port installed, and my XF86Config file contains: Section Module Load freetype Load type1 EndSection I think that fits the bill, but obviously something is wrong... -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
gdkxft + gnome 1.4 + gdm on FreeBSD 4.7p3
Well, the directions claim its simple, but try as I might, I can't get font anti-aliasing to save my life! I've tried following the gdkxft README, but I still can't make gdkxft do anything useful. Is there some trick to getting it working with gdm? Should I have an Xsession.d or an xinitrc.d directory somewhere (creating them in /etc/X11 doesn't do squat). Thanks! Sorry in advance if this is a moronic question. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: gdkxft + gnome 1.4 + gdm on FreeBSD 4.7p3
On Monday, February 3, 2003, at 09:24 AM, Joe Marcus Clarke wrote: On Mon, 2003-02-03 at 03:16, Mark Edwards wrote: Well, the directions claim its simple, but try as I might, I can't get font anti-aliasing to save my life! I've tried following the gdkxft README, but I still can't make gdkxft do anything useful. Is there some trick to getting it working with gdm? Should I have an Xsession.d or an xinitrc.d directory somewhere (creating them in /etc/X11 doesn't do squat). You will need to move the gdm startup out of /etc/ttys, and create a /usr/X11R6/etc/rc.d script for it. In that script, set the LD_PRELOAD (I think that's what gdkxft requires) variable, and you should be good to go. Joe Can you point me to a description of how to do this? All the documentation I've found describes starting gdm from /etc/ttys, and I'm not exactly sure how to translate that over to an rc.d script. Also, will setting LD_PRELOAD this way affect gnome after login, or will it just affect gdm? I tried setting LD_PRELOAD by hand in a term window after logging in, and then launching a gnome app like mozilla, and I still didn't see anti-aliased text. Does this indicate further problems? Thanks for you help! -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: gdkxft + gnome 1.4 + gdm on FreeBSD 4.7p3
On Monday, February 3, 2003, at 09:32 PM, Joe Marcus Clarke wrote: I have no idea. I've never used gdkxft. However, if you read the gdkxft webpage, you'll see there's a Mozilla patch for it: http://gdkxft.sourceforge.net/gdkxft-mozilla.html Did you apply this patch? If you have further problems, I recommend checking out: http://gdkxft.sourceforge.net/README Or better yet, upgrade to GNOME 2 which has anti-aliased support built in (note, so does Mozilla now). Ah, perhaps that's a good call. I was shying away from it since I'm running on a Pentium Pro 180, but from the release notes at gnome.org, it looks like gnome2 is faster even on older hardware. Thanks for the advice! -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
inetd/hostname failures
I've recently started having the following show up in my security run output: lilbuddy.antsclimbtree.com kernel log messages: me: getaddrinfo(adsl-66-122-112-170.dsl.snfc21.pacbell.net, AF_INET) failed I also had failures of the following kind: Nov 7 08:33:34 lilbuddy inetd[68076]: refused connection from 63.202.185.83, service imapd (tcp) Nov 7 12:18:43 lilbuddy inetd[69441]: refused connection from 66.122.112.170, service imapd (tcp) I worked around the inetd issue by commenting out the following in /etc/hosts.allow: #ALL : PARANOID : RFC931 20 : deny The thing is both of the IP's in question (66.122.112.170 and 63.202.185.83) have been connecting daily with no problem whatsoever for over a year. All of a sudden these refusals started, and I haven't changed anything on my end. My questions: 1) What is the best way to troubleshoot the getaddrinfo failure above? What is the failure, exactly? Poking around with nslookup and dig doesn't reveal anything, at least to me. 2) The inetd failure seems related to the IP's in question not having the same reverse/forward DNS entries. However, this has been the case for over a year and I haven't had the failure until recently. What has changed to cause this failure? 3) Is disabling ALL : PARANOID : RFC931 20 : deny a bad idea? One interesting thing is that both of these IP addresses are owned by pacbell.net. My guess is that pacbell messed something up on their end. I run the network at 66.122.112.170, and nothing significant has changed. I tweaked the firewall there, but disabling it doesn't change anything so I don't think it is related to the firewall. I'm not looking forward to trying to explain this to pacbell ... Thanks for any suggestions. Please CC me in any replies, as I'm on the digest. -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
