named won't bind to external interface and ignores other options.
bind 9.4.2/FreeBSD 7.0 seems to be ignoring many settings I enter in
/etc/namedb/named.conf. zones are being properly served internally, but
can't query or transfer from the outside.
listen-on {216.154.117.227; 192.168.1.1;};
listen-on-v6 { none; };
tcp6 0 0 ::1.953*.*LISTEN
tcp4 0 0 127.0.0.1.953 *.*LISTEN
tcp4 0 0 192.168.1.1.53 *.*LISTEN
any ideas ?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: libc5 on freebsd 6.3
Thank you for your response, but it doesn't really help with the situation, besides the software I'm talking about has been recompiled many time over since the upgrade. Just to make sure, I recompiled again and it linked to both libc5 and libc6 right away. That's my issue. [EMAIL PROTECTED] wrote: after several years of relatively trouble free system ( 5 6.3 ) and port upgrades, I started having some issues with timesieved daemon of cyrus imap. nothing in the software configuration has changed, but the cyrus port was recently upgraded ( around the same time that the system was upgraded from 6.2 to 6.3 ) the only thing that looks suspicious is the fact that most ( or all ) cyrus binaries are linked to both libc5 and libc6. in fact, after some digging around, I discovered that many other binaries on the system seem be linked to both libraries. I suspect that libc5 is the remnant of 5x installation. What's the safest thing to do ? remove libc5 and link libc5 to libc6 ? rebuild affected software ? ( couldn't find a relevant make.conf option, so what might a flag like that look like ? WITH_LIBC_VER=6 ? You have to recompile all your installed ports as part of your upgrade to a new version of FreeBSD (e.g. 5.x - 6.x, 6.x - 7.x, etc). The only reason this is necessary is to prevent this kind of problem from creeping in as you incrementally rebuild your ports over time. Binaries linked to incompatible or inconsistent sets of libraries like two different versions of libc will behave unpredictably and may crash. No special care needs to be taken when recompiling, just make sure to recompile everything (portupgrade -fa or -faPP or similar). Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
libc5 on freebsd 6.3
after several years of relatively trouble free system ( 5 6.3 ) and port upgrades, I started having some issues with timesieved daemon of cyrus imap. nothing in the software configuration has changed, but the cyrus port was recently upgraded ( around the same time that the system was upgraded from 6.2 to 6.3 ) the only thing that looks suspicious is the fact that most ( or all ) cyrus binaries are linked to both libc5 and libc6. in fact, after some digging around, I discovered that many other binaries on the system seem be linked to both libraries. I suspect that libc5 is the remnant of 5x installation. What's the safest thing to do ? remove libc5 and link libc5 to libc6 ? rebuild affected software ? ( couldn't find a relevant make.conf option, so what might a flag like that look like ? WITH_LIBC_VER=6 ? or is there something else that can be done ? also, it would be helpful to learn how to avoid this in the future. Thanks a lot in advance. /usr/local/cyrus/bin/timsieved: libsasl2.so.2 = /usr/local/lib/libsasl2.so.2 (0x8814b000) libgssapi.so.8 = /usr/lib/libgssapi.so.8 (0x88162000) libkrb5.so.8 = /usr/lib/libkrb5.so.8 (0x88171000) libasn1.so.8 = /usr/lib/libasn1.so.8 (0x881ab000) libroken.so.8 = /usr/lib/libroken.so.8 (0x881d3000) libcrypt.so.3 = /lib/libcrypt.so.3 (0x881e) libcom_err.so.3 = /usr/lib/libcom_err.so.3 (0x881f9000) libdb-4.2.so.2 = /usr/local/lib/libdb-4.2.so.2 (0x881fb000) libssl.so.4 = /usr/lib/libssl.so.4 (0x882d) libcrypto.so.4 = /lib/libcrypto.so.4 (0x88302000) libmd.so.3 = /lib/libmd.so.3 (0x8840f000) libwrap.so.4 = /usr/lib/libwrap.so.4 (0x8841e000) libc.so.6 = /lib/libc.so.6 (0x88425000) libc.so.5 = /lib/libc.so.5 (0x8851c000) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
no innodb support in mysql 5.0 port
compiled with default options ( not setting WITHOUT_INNODB ), but when I start the server, I can't create or convert any tables to InnoDB format. I tried various my.cf files ( including my-innodb-heavy-4G.cnf and without any cnf files, show engine innodb status; ERROR 1235 (42000): Cannot call SHOW INNODB STATUS because skip-innodb is defined show engines; | InnoDB | DISABLED | Supports transactions, row-level locking, and foreign keys How do I get InnoDB working ? please help !! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
amd64 build on xeon
Looking around in /usr/src/sys/amd64/conf/, I only see one cpu option - HAMMER. I found some references to CPUTYPE=nocona for make.conf, but what cpu option do I use for Intel 86x64 platform for kernel builds ? thank you all. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
installing on lsi sata 150-6
When I try to install Freebsd on LSI sata 150-6 mirror volumes with 5.4 or
6.0 media, I get the same No root device found - you must label a
partition as / in label editor. The slice was allocated and labels
created in both cases. If I try to write the changes from the label menu,
I get unable to find /dev/amrd0s1{a,b,c,d}. If I allocate a separate
slice for each partition, the same thing happens, only the device names
change slightly.
The volumes themselves get detected properly at install boot and all show
up in both slice and label menus. oh what to do, what to do ? Does
anyone have root residing on one of these controller volumes ?
Thank you all.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum setup
nevermind. I figured this out. still, Greg is one smart guy :). I just wish disklabel was at least a bit more user friendly. Every time I use it I have to understand it all over :) /boot/loader.conf vinum_load=YES vinum.root=root vinum.drives=/dev/ad2 /dev/ad3 synrat wrote: thanx Greg, you're right as always. I booted into single user from start up and sure enough everything was editable then. I got another problem though. I set up 2 disks for vinum and want to allocate exisiting partitions to vinum mirrored volumes. I left 16 blocks at the begining, moved first partition ( swap ) to 281, recalculated offsets in vinum config with -16, run vinum config, everything's peachy, drives rebuild, fsck sees no errors, I edit fstab, reboot, vinum module loads but root can not be mounted as a vinum device, I still have to manually specify my regular root ( /dev/das1a ) partition. dmesg output below and vinum/disklabel too. thanx a million. Greg for US president :) Mounting root from ufs:/dev/vinum/root missing unit number setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 disklabel ( similar for both disks ) - a: 21094400 21094404.2BSD 2048 1638489 # (Cyl. 131*- 1444*) b: 2109159 281 swap# (Cyl.0*- 131*) c: 1562481270unused0 0# (Cyl.0 - 9725*) e: 133044287 232038404.2BSD 2048 1638489 # (Cyl. 1444*- 9725*) h: 156248111 16 vinum # (Cyl.0*- 9725*) vinum -- drive a device /dev/ad2s1h drive b device /dev/ad3s1h volume root plex org concat sd length 21094400s driveoffset 2109424s drive a plex org concat sd length 21094400s driveoffset 2109424s drive volume home plex org concat sd length 133044287s driveoffset 23203824s drive a plex org concat sd length 133044287s driveoffset 23203824s drive b On Fri, 18 Jun 2004, Greg 'groggy' Lehey wrote: [Format recovered--see http://www.lemis.com/email/email-format.html] Output wrapped. On Thursday, 17 June 2004 at 12:04:01 -0400, synrat wrote: 4.8 I'm trying to setup partitions for vinum. I am in single user mode, but every time I try to modify swap size to accomodate for vinum confuration I get disklabel: ioctl DIOCWDINFO: open partition would move or shrink re-edit the label? [y] #size offsetfstype [fsize bsize bps/cpg] a: 21094400 21094404.2BSD 2048 1638489 # (Cyl. 131*- 1444*) b: 2109000 430 swap# (Cyl.0 - 131*) c: 1562481270unused0 0# (Cyl.0 - 9725*) e: 133044287 232038404.2BSD 2048 1638489 # (Cyl. 1444*- 9725*) h: 156248111 16 vinum # (Cyl.0*- 9725*) You can't change open partitions. You also can't unmount swap. If you go from multi-user to single user mode, the swap remains mounted. You'll need to boot to single user mode to do that. If this doesn't answer your question, more details, please, including any log messages. Please don't wrap them. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. ___ [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]
ISPs blocking SMTP connections from dynamic IP address space
Hi Nicole I wonder if you can help me. I saw your message on the Net regarding ISPs Blocking SMTP connections from dynamic IP address space. I have a problem now that didn't exist 6 months where my mail gets returned when emailing a specific address, the error is 550: SPAMMER and all my ISP will say it's the remote end that's blocking. Is this what your talking about, and if yes how can I check who's doing what? Thanks Lenny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
