hi darcy, was about to type away some thoughts, but glad you solved it.
now my own question: how is using a Mac mini DC with Mac OS X 10.4.10 Server and has compiled ClamAV 0.91.1 and uses it daily? i recognized have some weird behaviour, when it scans (as it seems) attachements which are encoded in a octet-stream. a typical line from the logs would look like: Jul 27 13:42:27 mail amavis[13802]: (13802-01) p003 1/1/2 Content- Type: application/octet-stream, size: 646241 B, name: this lets my clamd crash (but not die, as it still lurks around and starts too hog the cpu as much as it can, while the kernel takes the rest of cpu time). only a kill -9 clamd brings all back to normal levels and it works ok until the next attachement with the sam eencoding comes around. any glues? i could dsend a simple email with an excel file attached, which brings my clamd down (if wished). hope here are some Mac users with a similar setup. thx. oliver Am 27.07.2007 um 22:39 schrieb darcy w. christ: > hi everyone, > > solved my own problem. turns out that install was failing because > of a funky acl. > > > > On Jul 27, 2007, at 12:59 PM, darcy w. christ wrote: > >> hi everyone, >> >> i'm having trouble with the make install command on mac os x (v >> 10.4.10). >> >> here's the error i am seeing: >> >> $ sudo make install >> Making install in libclamav >> test -z "/usr/local/lib" || /bin/sh ../mkinstalldirs "/usr/local/lib" >> /bin/sh ../libtool --mode=install /usr/bin/install -c 'libclamav.la' >> '/usr/local/lib/libclamav.la' >> /usr/bin/install -c .libs/libclamav.lai /usr/local/lib/libclamav.la >> /usr/bin/install -c .libs/libclamav.a /usr/local/lib/libclamav.a >> chmod 644 /usr/local/lib/libclamav.a >> ranlib /usr/local/lib/libclamav.a >> --------------------------------------------------------------------- >> - >> Libraries have been installed in: >> /usr/local/lib >> >> If you ever happen to want to link against installed libraries >> in a given directory, LIBDIR, you must either use libtool, and >> specify the full pathname of the library, or use the `-LLIBDIR' >> flag during linking and do at least one of the following: >> - add LIBDIR to the `DYLD_LIBRARY_PATH' environment variable >> during execution >> >> See any operating system documentation about shared libraries for >> more information, such as the ld(1) and ld.so(8) manual pages. >> --------------------------------------------------------------------- >> - >> test -z "/usr/local/include" || /bin/sh ../mkinstalldirs "/usr/local/ >> include" >> /usr/bin/install -c -m 644 'clamav.h' '/usr/local/include/clamav.h' >> Making install in clamscan >> test -z "/usr/local/bin" || /bin/sh ../mkinstalldirs "/usr/local/bin" >> /bin/sh ../libtool --mode=install /usr/bin/install -c >> 'clamscan' '/ >> usr/local/bin/clamscan' >> /usr/bin/install -c clamscan /usr/local/bin/clamscan >> ../libtool: line 1: 8527 Bus error /usr/bin/install -c >> $stripme $file $destfile >> make[2]: *** [install-binPROGRAMS] Error 1 >> make[1]: *** [install-am] Error 2 >> make: *** [install-recursive] Error 1 >> >> >> any suggestions? i tried to send my configure and make output as >> well, but the message was too large to get through to the maillist. >> i can send it to anyone who wants to see it. >> >> thanks - i appreciate any help. >> >> >> >> ~/darcy w. christ >> 1000camels >> >> >> _______________________________________________ >> Help us build a comprehensive ClamAV guide: visit http:// >> wiki.clamav.net >> http://lurker.clamav.net/list/clamav-users.html >> > > > ~/darcy w. christ > 1000camels > > > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http:// > wiki.clamav.net > http://lurker.clamav.net/list/clamav-users.html > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
