Re: Compile courier-imap 4.1.1 fails (solved)
(Sent off-group): The biggest thing is that if you have libs in non-standard locations then you need to set LDFLAGS CPPFLAGS CFLAGS appropriately before you compile for tcsh/csh % setenv LDFLAGS -L/usr/mylibs % setenv CPPFLAGS -I/usr/myincludes % setenv CFLAGS -I/usr/myincludes Chad Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net Chad, Thank you for your advice. I got there in the end, and cc the group for others' future reference (and mine): $setenv LDFLAGS "-L/usr/local/lib -L/usr/local/include -L/usr/include/openssl" $setenv CPPFLAGS "-I/usr/local/lib -I/usr/local/include -I/usr/include/openssl" $setenv CFLAGS "-I/usr/local/lib -I/usr/local/include -I/usr/include/openssl" (where -I = big i not small L) $./configure --without-authdaemon --with-authvchkpw --enable-unicode=iso-8859-1,iso-8859-15,utf-8 --without-ipv6 --enable-workarounds-for-imap-client-bugs now... $make check Lots of complaints about FAM (which *is* installed, but "not configured properly"). I browsed a few posts wrt FAM, which led me to continue anyway, since it seems most applicable to many-user systems, particularly with shared folders. So, finally: $./configure --without-authdaemon --with-authvchkpw --enable-unicode=iso-8859-1,iso-8859-15,utf-8 --without-ipv6 --enable-workarounds-for-imap-client-bugs $make check (More complaints expected due to --enable-workarounds... as documented), then: #make install #make install configure Up and running after a few tweaks, and first imap mails sent. Thank you! Imap over TLS/SSL next, then Sqwebmail Best wishes boink ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compile courier-imap 4.1.1 fails (/usr/bin/ld: cannot find -lpcre)
On 06/06/06, Juha Saarinen <[EMAIL PROTECTED]> wrote: Why not use courier-imap from the ports collection? Juha, Thank you for your prompt response. As I mentioned, the port also *apparently* fails to find pcre: conftest.c:33:23: pcre/pcre.h: No such file or directory In addition, by default, the port includes options I don't want, and omits some that I do want (although I could change this). Risk averse, I don't want to proceed without either fixing the problem building from source, or continuing with the port, assured not to have problems later. Still stuck! Can anyone help? boink ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Compile courier-imap 4.1.1 fails (/usr/bin/ld: cannot find -lpcre)
Dear all, I'm building a pop toaster, have qmail up and running, vpopmail too, now trying to get courier-imap-4.1.1 working. Platform: FreeBSD 6.0_RELEASE, GENERIC kernel. Problem: when installing from source, ./configure works OK (non-root, as advised): $./configure --without-authdaemon --with-authvchkpw --enable-unicode=iso-8859-1,iso-8859-15,utf-8 but... $make check Linking maildirmake Linking testmaildirfilter /usr/bin/ld: cannot find -lpcre *** Error code 1 Stop in /usr/download/qmail/courier-imap-4.1.1/maildir. *** Error code 1 Stop in /usr/download/qmail/courier-imap-4.1.1/maildir. *** Error code 1 maildir/Makefile has: ... CPPFLAGS = -I/usr/local/include -I/usr/local/include ... CXXFLAGS = -I/usr/local/include -I/usr/local/include -Wall ... LDFLAGS = -L/usr/local/lib -L/usr/local/lib -rpath=/usr/lib:/usr/local/lib ... Is there any reason these should be specified twice? Why doesn't LDFLAGS mention /usr/local/include - which is where my pcre.h is? Still working with the source, I tried: $ env -v "LDFLAGS=-L/usr/local/lib -L/usr/local/include -rpath=/usr/lib:/usr/local/lib:/usr/local/include" ./configure --without-authdaemon --with-authvchkpw --enable-unicode=iso-8859-1,iso-8859-15,utf-8 which fails with: checking pcre.h usability... yes checking pcre.h presence... yes checking for pcre.h... yes checking pcre/pcre.h usability... no checking pcre/pcre.h presence... no checking for pcre/pcre.h... no checking for pcre.h... (cached) yes checking for pcre/pcre.h... (cached) no checking for FAMOpen in -lfam... yes checking for fam.h... (cached) no configure: WARNING: The development header files and libraries for fam, configure: WARNING: the File Alteration Monitor, are not installed. configure: WARNING: You appear to have the FAM runtime libraries installed, configure: WARNING: so you need to simply install the additional development configure: WARNING: package for your operating system. configure: error: FAM development libraries not found. configure: error: /usr/local/bin/bash './configure' failed for maildir # locate fam.h /usr/local/include/fam.h Furthermore, when using the port, the installation completes without any warnings, but in /usr/ports/mail/courier-imap/work/courier-imap-4.1.1/maildir/config.log, I see: ... | #include configure:21219: result: no configure:21223: checking pcre/pcre.h presence configure:21233: cc -E -I/usr/local/include -I/usr/local/include conftest.c conftest.c:33:23: pcre/pcre.h: No such file or directory configure:21239: $? = 1 configure: failed program was: | /* confdefs.h. */ ... ...so I presume that anything that relies on pcre will fail with the port, too. After hours of fruitless Googling, I'm completely stuck. I don't want to use the port, ignore the error, and have problems later. Can someone help me out? With thanks in advance, boink PS - I was unable to subscribe to the courier-mta list at Sourceforge (no confirmation received), hence the post here. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ignorant user overfilled /usr; strange errors followed. Fixed with fsck -y, but what exactly happened?
On 18/05/06, Lowell Gilbert <[EMAIL PROTECTED]> wrote: boink <[EMAIL PROTECTED]> writes: 8<... > My questions are these: > - How could /usr have been at 108%, given that 100% is the logical maximum? Because that *isn't* a given. See the FAQ entry on "How is it possible for a partition to be more than 100% full?" > - Is there any risk that a physically adjacent filesystem be > damaged? No. Furthermore, it's unlikely that your /usr was actually damaged, either. Don't run fsck on a live filesystem; of *course* it will always find "errors." > - How can it be that, immediately following the deletion of > /usr/ports/ktrace.out, I still had errors *at all* (prior to the > fsck)? See the FAQ entry on "The du and df commands show different amounts of disk space available. What is going on?" That describes what you probably should have done instead of the fsck. > - Given its recent history, can I now trust the integrity of /usr? Probably. But you may have messed it up with the fsck, so just to be sure, go into single-user mode, umount /usr, and fsck it WHILE IT IS NOT MOUNTED. > My interpretation of the situation is that following the deletion of > /usr/ports/ktrace.out, KDE, on startup, tried to write a file to a > filesystem that apparently (although incorrectly) had no free blocks. > fsck fixed the problem of the reported free blocks. More or less. But since the kernel's idea of what was on the disk no longer matched reality (i.e., it knew that in reality there *were* no free blocks), you may have gotten into trouble. > However, if this interpretation is correct, it shouldn't have worked > *at all* until fsck had repaired the filesystem. That is, KDE should > not have started at all. That doesn't necessarily follow. > So, prior to the fsck -y in single-user mode, what was happening in > the five minutes it took KDE to start? I don't know KDE at all, but my guess would be some kind of timeout. Lowell, Thank you for taking the time to answer my questions. I omitted to mention that I had rebooted into single user mode prior to running fsck, so /usr was not in fact mounted when fsck was run. The du/df FAQ is interesting, and non-obvious, as is FAQ 9.26. (How is it possible for a partition to be more than 100% full?), which explains why the quoted disk usage was 108%. http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html. Thanks again, boink ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ignorant user overfilled /usr; strange errors followed. Fixed with fsck -y, but what exactly happened?
Dear FreeBSD, While attempting to follow filesystem activity (and not realising the effect it would have) I left a ktrace running (something like ktrace -di -p0 -ti - seen on a forum while searching for a Filemon equivalent for FreeBSD). I had launched it while in /usr/ports, and forgot about it. Doh! Some time later strange things started happening, so I exited from X/KDE, and found a whole sequence of 'filesystem is full' errors on the console. df said that /usr was at 108%. I found the offending ktrace.out file in /usr/ports (~25GB), killed ktrace, deleted the file, and restarted X/KDE. It took about 5 minutes to show the desktop, following a number of console messages like 'xauth: creating new authority file...' So, I Googled around and found a few hints relating to permissions in ~, but that didn't seem to be the problem; anyway I moved my ~/.kde/ to ~/.kde_20060515 in an attempt to 'reset' kde's startup behaviour, but X/KDE still took ages to start the GUI, following similar messages. Even once X/KDE had started, some applications took a *long* time to start (eg Firefox - 3/4 minutes to show blank home page). However, I could still r/w access all files within /usr. Following the advice found on various fora, I then ran fsck -y in single-user mode, with the following output: ** Last mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? yes 401256 files, 4135860 used, 13715938 free (126762 frags, 169-647 blocks, 0,8% fragmentation) Afterwards, X/KDE started with its usual alacrity, so I restored my ~/.kde folder, and now everything seems to be exactly as before. My questions are these: - How could /usr have been at 108%, given that 100% is the logical maximum? - Is there any risk that a physically adjacent filesystem be damaged? - How can it be that, immediately following the deletion of /usr/ports/ktrace.out, I still had errors *at all* (prior to the fsck)? - Given its recent history, can I now trust the integrity of /usr? My interpretation of the situation is that following the deletion of /usr/ports/ktrace.out, KDE, on startup, tried to write a file to a filesystem that apparently (although incorrectly) had no free blocks. fsck fixed the problem of the reported free blocks. However, if this interpretation is correct, it shouldn't have worked *at all* until fsck had repaired the filesystem. That is, KDE should not have started at all. So, prior to the fsck -y in single-user mode, what was happening in the five minutes it took KDE to start? Sorry if this whole description was long and convoluted, but I'd really appreciate a few hints as to what went on. With thanks in advance for any illumination, boink PS. Henceforth, I promise not to let commands I don't understand fill up my filesystems :o/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Solved: How can I tell what process is sending packets from a particular port (udp/55613)?
Frank, Glenn, Thank you for the *very* quick responses (to try sockstat -46p 55613). Actually, I had misread the source address (red face) - it's from someone else's machine with a similar IP I didn't recognise (second DSL was added earlier this week and a small co-hosting centre is now routed through my place). My humble apologies, but thank you both for the tip. Best wishes, boink ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hacked? How can I tell what process is sending packets from a particular port (udp/55613)?
Dear FreeBSD, I see outbound packets from udp/55613, one every 5 seconds, to a single non-routable (10) IP, with destination port increasing by 1 with each packet, with expected ICMP Destination net unreachables from an upstream router. AFAIK, there's no reason for this and I don't like it - how can I tell which process is sending the packets? With thanks in advance, boink ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: arp -a takes 40 secs to display cached MAC addresses. Is thisnormal?
Matt, You're absolutely right - thank you. Best wishes, boink On 04/04/06, Matt Emmerton <[EMAIL PROTECTED]> wrote: > > > - Original Message - > From: "boink" <[EMAIL PROTECTED]> > To: > Sent: Monday, April 03, 2006 6:06 PM > Subject: arp -a takes 40 secs to display cached MAC addresses. Is > thisnormal? > > > Dear FreeBSD, > > # uname -a > FreeBSD MyFBSD.int.vir 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 > 09:36:13 UTC 2005 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > # /usr/bin/time -h arp -a > MyFBSD (10.1.2.1) at 00:00:f8:10:6c:8a on dc0 permanent [ethernet] > MyFirewall (10.1.2.254) at 00:0d:b9:11:a5:b9 on dc0 [ethernet] > ? (10.1.2.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] > 40.22s real 0.00s user 0.00s sys >^ > ...where: > > > > arp is attempting to do a reverse-DNS lookup on 10.1.2.255. No answer is > received from your DNS server in the allowable time-out interval, so it > displays the name as '?'. > > Redo the same test using 'arp -a -n' and you'll see it complete > immediately. > > -- > Matt Emmerton > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
arp -a takes 40 secs to display cached MAC addresses. Is this normal?
Dear FreeBSD, # uname -a FreeBSD MyFBSD.int.vir 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # /usr/bin/time -h arp -a MyFBSD (10.1.2.1) at 00:00:f8:10:6c:8a on dc0 permanent [ethernet] MyFirewall (10.1.2.254) at 00:0d:b9:11:a5:b9 on dc0 [ethernet] ? (10.1.2.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] 40.22s real 0.00s user 0.00s sys ^ ...where: # ifconfig dc0: flags=8843 mtu 1500 options=8 inet6 fe80::200:ff8f:fe01:6a3a%dc0 prefixlen 64 scopeid 0x1 inet 10.1.2.1 netmask 0xff00 broadcast 10.1.2.255 ether 00:00:f8:10:6c:8a media: Ethernet autoselect (100baseTX ) status: active rl0: flags=8843 mtu 1500 options=8 inet6 fe80::240:f4ff:fec3:54f5%rl0 prefixlen 64 scopeid 0x2 inet 10.1.1.98 netmask 0xff00 broadcast 10.1.1.255 ether 00:40:f4:c4:a4:6e media: Ethernet autoselect (100baseTX ) status: active ed0: flags=8943 mtu 1500 inet6 fe80::2e0:7dff:fe43:e259%ed0 prefixlen 64 scopeid 0x3 ether 00:e0:7d:67:5e:a8 media: Ethernet autoselect (10baseT/UTP) plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet 127.0.0.1 netmask 0xff00 Notes: - everything else on 10.1.[1,2].0/24 is switched off currently - the arp list is in fact complete - ed0 has no IP address (outside the firewall, for sniffing purposes) - I'm not experiencing any networking issues - IIRC this happened on Free BSD5.3, too Is this expected behaviour? Just curious. Best wishes, boink __ __ __ \ / __ / \ | / \ \ \|/ _,.---v---. /\__/\ /\ save the \_ _/ / \ humans! \ \_| @ __| / hjw \\_ `97 \ ,__/ / ~~~`~~/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can FreeBSD safely use a (un-booted from) drive that is invisible to the BIOS?
Danny, FWIW, my FBSD 6 is running on a new "80GB" IDE disk my Asus A7V266 (Athlon mobo from end-2001) thought was 8GB in size. I set the disk type to manual in the (latest) BIOS, and defined the geometry as seen by sysinstall. It's the only device on the primary channel, running as master, CD-ROM is on the secondary. The system boots (no dual boot) and runs fine, although the drive isn't listed by the BIOS at POST (the CD-ROM is) and all disk is visible to FBSD: # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a496M126M330M28%/ /dev/ad0s1d496M974K455M 0%/tmp /dev/ad0s1e 34G7.0G 24G22%/usr /dev/ad0s1f 34G4.5G 27G14%/var However... # cat /var/log/dmesg.yesterday | grep ad0 ad0: setting PIO4 on VIA 8233 chip ad0: setting UDMA100 on VIA 8233 chip ad0: 76319MB at ata0-master UDMA100 ad0: 156301488 sectors [155061C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 ad0: VIA check1 failed ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed Trying to mount root from ufs:/dev/ad0s1a ... which it then succeeds to do. I'm not sure how to interpret the 'check1 failed' notices, or what GEOM means by 'new disk' at every boot; but as it works, I'm leaving it alone. I'm not sure if this helps. Why don't you partition the drive, copy whatever data you have on ad0 to it, move it to another machine, and see what happens? At least at this point you have nothing to lose. Best wishes, boink ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
