Running KDE 3.4 in FreBSD 5.2.1 (libm.so.3 not found)

[John Cholewa]

I updated the version of KDE on my box (5.2.1-RELEASE) to 3.4, and I'm 
getting the following result when running vncserver:


> Could not open library kcminit.la: Shared object "libm.so.3" not found
> /libexec/ld-elf.so.1: Shared object "libm.so.3" not found
> Could not open library ksmserver.la: Shared object "libm.so.3" not found
> /libexec/ld-elf.so.1: Shared object "libm.so.3" not found
> startkde: Shutting down...

I found that I have libm.so.2, and I tried to find out how I could 
update that file.  I had presumed that updating KDE itself would 
recursively handle it (I cvsup then do make clean && make && make 
install in the port's directory).  But now a web search of this 
particular problem suggests that the only way to fix it is to update the 
entire OS, and I don't want to do that.  Things break when I try to do 
major updates (I had huge nightmares when I upped versions of php and 
perl to 5 and 5.8, respectively), and my server setup is smooth enough 
that I don't want to take any unnecessary risks to get client apps to work.


So is there a port that will provide this file?


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

autoblocking many ssh failed logins from the same IP....

[John Cholewa]

Jun 30 10:36:05 phantom sshd[70478]: Failed password for news from 
212.88.182.121 port 51218 ssh2
Jun 30 10:36:16 phantom sshd[70500]: Failed password for sshd from 
212.88.182.121 port 51608 ssh2
Jun 30 10:36:39 phantom sshd[70569]: Failed password for root from 
212.88.182.121 port 52297 ssh2

I get the above a lot in my logs (except more of it).  Each day, a couple 
hundred failed attempts to log in from one or sometimes two IP addresses shows 
up.  I don't have anything like ipf running, and since this machine is about 
fifteen hundred miles away from me, I don't want to experiment with software 
firewalling right now.

That known, is there any way to tell sshd (or some more powerful daemon) to 
stop accepting login attempts from a given IP if it tries and fails to log in 
too many times in a limited duration (like in the same minute)?

I suppose, now that I'm thinking about it, that it'd be best to actually just 
read the man pages and figure out how to get sshd to ignore any attempt to 
attach from ports other than 22.  I mean, why are other machines trying to ssh 
in at ports over fifty thousand anyway?

--
 -JC
 http://www.livejournal.com/users/jcholewa/

PS:  Oh, yeah ... "FreeBSD 4.8-RELEASE #0: Thu Apr  3 10:53:38 GMT 2003" ; 
openssh-3.6.1_5 ; openssl-0.9.7d_1



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

how to manage qmail queue warnings?

[John Cholewa]

I know that the queuelifetime control file sets the time before qmail 
gives up sending a message (usually 1 week), but how do I modify the 
warning that is usually set to notify the user four hours after sending 
that the message is being held back?

--
 -JC
 http://www.jc-news.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Stop in /usr/ports/graphics/ImageMagick

[John Cholewa]

===>   giFT-0.11.6 depends on shared library: Magick.6 - not found
===>Verifying install for Magick.6 in /usr/ports/graphics/ImageMagick
===>  ImageMagick-6.0.6.2 has known vulnerabilities:
>> ImageMagick -- EXIF parser buffer overflow.
   Reference: 

>> Please update your ports tree and try again.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick.
*** Error code 1
Stop in /usr/ports/net/gift.

Aargh.  Over the past week or two, I've cvsupped several times, but I 
keep getting this.

I'm using 5.2.1, and I've tried this using both "portinstall", 
"portinstall -P" and "make" (while in both "/usr/ports/net/gift" and 
"/usr/ports/graphics/ImageMagick").  And I've "make clean"ed beforehand.

Nothing relevant seems to be listed in /usr/ports/UPDATING.  Any 
suggestions?

--
 -JC
 http://www.jc-news.com/parse.cgi?coding/main
 http://www.jc-news.com/coding/freedom/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

qt3 not compiling in ports?

[John Cholewa]

When trying to install kde3 (running "make clean; make" in 
/usr/ports/x11/kde3 and deselecting all optional features), I get the 
following error:

install  -s -o root -g wheel -m 555 
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.3/tools/qvfb/qvfb 
/usr/X11R6/bin
cd src/moc && make
c++ -c -pipe -fno-exceptions -O -pipe -mcpu=pentiumpro  -DQT_MOC 
-DQT_NO_CODECS -DQT_LITE_UNICODE -DQT_NO_COMPONENT -DQT_NO_STL 
-DQT_NO_COMPRESS -I -I. -I/usr/local/include/freetype2 
-I/usr/local/include -I../../include -I../tools -I. -I/usr/local/include 
-o ./moc_yacc.o moc_yacc.cpp
moc.y:58:27: qplatformdefs.h: No such file or directory
*** Error code 1

Stop in /usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.3/src/moc.

Should I try separately installing qt instead of relying on dependency 
resolution?  That's what I'll be trying next, but I wanted to know if 
anybody has heard of problems building this.

On the side, anybody have links to ports error reports?  I had the pages 
for this bookmarked a long time ago, but I don't think I have that 
bookmark file lying around now.  :/

--
 -JC
 http://www.jc-news.com/parse.cgi?coding/main
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

portupgrade running slower than before?

[John Cholewa]

I started "portupgrade -ra" on my home mail server (FreeBSD 
5.2.1-RELEASE) two or three hours ago.  It says "[Updating the pkgdb 
 in /var/db/pkg ... - 246 packages found (-0 +1) . 
done]", and the output hasn't changed since.  For much of this time, 
ruby18 has been using 90% of my system's resources.  It's obviously 
doing *something*, but I can't see any ironclad progress in terms of 
packages being updated.

As recently as a few weeks ago, running this same thing would start 
installing programs within minutes at most.  The only major change that 
I've made in the past couple weeks is getting rid of stale 
dependencies.  Most of these were caused by XFree86-Libraries (staled as 
xorg-libraries), so I just uninstalled and reinstalled (from ports, 
naturally) X.

Anyway, is this normal?  Should I set my machine to upgrade to 
FreeBSD-5.3 or something like that?  I did a "cvsup ports-supfile && 
portsdb -uU" the other day.  Should I do anything following that?

Thanks in advance.  :)
--
 -JC
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Any problems with php 4.3.8_2

[John Cholewa]

Hi,
I upgraded the php4 port on this 4.8-RELEASE box to 4.3.8_2.  I'm also 
using apache+mod_ssl-1.3.31+2.8.19.

When the lines
LoadModule php4_modulelibexec/apache/libphp4.so
AddModule mod_php4.c
are uncommented, apache segfaults on startup.
We're not in a position to upgrade to a newer version of FreeBSD, given 
that this box is a thousand miles away from us and I, being a novice in 
many respects, am considered the unquestioned unix/bsd/etc expert in 
this company (sadly, I wear too many hats for my employers to become 
genuinely experienced in any one thing).

I read in a recent post that installing php5 seems to be something that 
you install *instead* of "mod_php5 and "php5-cli".  Does the same apply 
for php4?  I ask because I have "mod_php4-4.3.8_2,1", "php4-4.3.8_2" and 
"php4-cli-4.3.8_2" installed here (as listed in "/var/db/pkg", all 
installed from ports)

Has anything simlar to what I've described been reported with newer 
versions of php?  Might I have installed conflicting packages?  Any 
suggestions will be welcomed.  :)

--
 -JC
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"