Re: named startup problems upgrading from 7.1p4 to 7.1p5 or 7.1p6
Sorry for starting a new thread with this - my ISP's mail server seems to rejecting all mail recipients when I send email with a mail client, so I'm having to use webmail instead. Their tech says they won't help - they only support Outlook! Grrr! On Sun, 28 Jun 2009 23:27:07 Matthew Seaman wrote: Ian wrote: Well the fact that if I run /etc/rc.d/named manually after the system has booted, the script also hangs suggests it's not the next process I have just check however ntpdate is the next one in the list to be started and that does start correctly - you can see it report the clock being adjusted. Also, when you do a Ctrl+C to break the named script on bootup, it says Script /etc/rc.d/named interrupted. Something I've just realised is that named stays loaded even when you 'break' the script. on bootup and DNS lookups work (I didn't think that was the case originally, but it is). Actually, some careful checking tonight shows that I had forgotten I had a second DNS server in resolv.conf that was doing the DNS resolution - in fact bind on this server is not working even though a bind process appears to be running :/ Hmmm Anything interesting from named in the system logs? You might want to enable /var/log/all.log by following the instructions in /etc/syslog.conf and then see what output you get by bouncing named. It's usually pretty good at pointing out exactly what it thinks the problem is. I've enabled all.log, it only shows the following output when starting named: Jun 29 20:51:43 msgserver named[1593]: starting BIND 9.4.2-P2 -t /var/named -u bind Jun 29 20:51:43 msgserver named[1593]: found 1 CPU, using 1 worker thread a ps axw | grep named gives the following output after running /etc/rc.d/named start: 1988 ?? Is 0:00.00 /usr/sbin/named -t /var/named -u bind 1930 p0 I+ 0:00.06 /bin/sh -x /etc/rc.d/named start 1987 p0 I+ 0:00.01 /usr/sbin/named -t /var/named -u bind and then after doing a Ctrl+C in the terminal where /etc/rc.d/named start is running, only one process continues to run: 1988 ?? Is 0:00.00 /usr/sbin/named -t /var/named -u bind This process doesn't respond to DNS queries, to rndc commands, to /etc/rc.d/named stop (says no process is running because there is no pid file being created) or by a kill command other than kill -9. (All named processes were killed before stating named) You could also try running: # /bin/sh -x /etc/rc.d/named start -- make sure named isn't running when you do that. There will be quite a lot of output as the rc system loads all of the various config files, but you should be able to trace exactly where it's got to when it does hang. Here's the edited highlights of output, I can't see anything that helps: + _rc_subr_loaded=: + name=named + rcvar=named_enable + command=/usr/sbin/named + extra_commands=reload + start_precmd=named_precmd + start_postcmd=make_symlinks + reload_cmd=named_reload + stop_cmd=named_stop + stop_postcmd=named_poststop + load_rc_config named + _name=named + [ -z named ] + false + [ -r /etc/defaults/rc.conf ] snip + named_enable=NO + named_program=/usr/sbin/named + named_pidfile=/var/run/named/pid + named_uid=bind + named_chrootdir=/var/named + named_chroot_autoupdate=YES + named_symlink_enable=YES snip + sourced_files=:/etc/rc.conf::/etc/rc.conf.local: + [ -r /etc/rc.conf.local ] + _rc_conf_loaded=true + [ -f /etc/rc.conf.d/named ] + required_dirs=/var/named + pidfile=/var/run/named/pid + command_args=-u bind + run_rc_command start + _return=0 + rc_arg=start + [ -z named ] + shift 1 + rc_extra_args= + _rc_prefix= + eval _override_command=$named_program + _override_command=/usr/sbin/named + command=/usr/sbin/named + _keywords=start stop restart rcvar reload + rc_pid= + _pidcmd= + _procname=/usr/sbin/named + [ -n /usr/sbin/named ] + [ -n /var/run/named/pid ] + _pidcmd=rc_pid=$(check_pidfile /var/run/named/pid /usr/sbin/named ) + [ -n rc_pid=$(check_pidfile /var/run/named/pid /usr/sbin/named ) ] + _keywords=start stop restart rcvar reload status poll + [ -z start ] + [ -n ] + eval rc_flags=$named_flags + rc_flags= + eval _chdir=$named_chdir _chroot=$named_chroot _nice=$named_nice _user=$named_user _group=$named_group _groups=$named_groups + _chdir= _chroot= _nice= _user= _group= _groups= + [ -n ] + [ -n named_enable -a start != rcvar ] + checkyesno named_enable + eval _value=$named_enable + _value=YES + debug checkyesno: named_enable is set to YES. + return 0 + eval rc_pid=$(check_pidfile /var/run/named/pid /usr/sbin/named ) + check_pidfile /var/run/named/pid /usr/sbin/named + _pidfile=/var/run/named/pid + _procname=/usr/sbin/named + _interpreter= + [ -z /var/run/named/pid -o -z /usr/sbin/named ] + [ ! -f /var/run/named/pid ] + debug pid file (/var/run/named/pid): not readable. + return + rc_pid= + [ start != start ] + eval _cmd=$start_cmd _precmd=$start_precmd
[SpamCop (66.51.128.45) id:3804161220][Trouble Ticket #190335] AutoReply: freebsd-questi..
[ SpamCop V2 ] This message is brief for your comfort. Please use links below for details. Unsolicited bounce from: 66.51.128.45 http://www.spamcop.net/w3m?i=z3804161220z6e70bfcff2bd738f22bff703440b764fz 66.51.128.45 appears to be sending unsolicited bounces, please see: http://www.spamcop.net/fom-serve/cache/329.html [ Offending message ] X-Claws-Bogosity: Ham, spamicity=0 [whitelisted] X-Apparently-To: ges...@yahoo.com via 68.142.207.115; Tue, 20 Jan 2009 22:41:07 -0800 X-YMailISG: .Dv8j18WLDtuJNxtWLhDpf5mpeWFUghNdv_egb_0fiZXg1RCIX735NHbTO4clF89wN6gneANUXqOut8aaecrNre7XPBoTfchA4NFlU0TRJqOCLU_mg0l5Z0_qbqu8xMJfpRn3An.qvcED777FwkCZQVEXN5Qa0vSW3Nm5cqisI_itxdD2dWcDmVt0oPwAE87AbDClIGtYWvkHHwS2kDGt_cGFpaZnbBIkxYHVXnWFcg8F8XH6v3K1DET2NtH5Am8wwm9un5sIVnxKYalYMlU7HHXa1itu7PXH7LbJRG3by.ydjpQN7TXysv8lExiTgdk4Kczs69igNPnXubTNINHACSpnufW_Sw- X-Originating-IP: [69.147.83.53] Authentication-Results: mta324.mail.re4.yahoo.com from=freebsd.org; domainkeys=neutral (no sig) Received: from 69.147.83.53 (EHLO mx2.freebsd.org) (69.147.83.53) by mta324.mail.re4.yahoo.com with SMTP; Tue, 20 Jan 2009 22:41:06 -0800 Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 8968B15F523; Wed, 21 Jan 2009 06:40:24 + (UTC) (envelope-from owner-freebsd-questi...@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 755D71065694; Wed, 21 Jan 2009 06:40:24 + (UTC) (envelope-from owner-freebsd-questi...@freebsd.org) Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B8901065676 for freebsd-questions@freebsd.org; Wed, 21 Jan 2009 06:40:06 + (UTC) (envelope-from apa...@tracker2.aebc.com) Received: from tracker2.aebc.com (xx6651128045.cipherkey.com [66.51.128.45]) by mx1.freebsd.org (Postfix) with ESMTP id 088C88FC34 for freebsd-questions@freebsd.org; Wed, 21 Jan 2009 06:40:05 + (UTC) (envelope-from apa...@tracker2.aebc.com) Received: from tracker2.aebc.com (localhost.localdomain [127.0.0.1]) by tracker2.aebc.com (Postfix) with ESMTP id AFD4D6768C8 for freebsd-questions@freebsd.org; Tue, 20 Jan 2009 22:38:41 -0800 (PST) Received: (from apa...@localhost) by tracker2.aebc.com (8.13.8/8.13.8/Submit) id n0L6cfin026492; Tue, 20 Jan 2009 22:38:41 -0800 From: AEBC Support via RT supp...@aebc.com In-Reply-To: 20090121063945.784f71065...@hub.freebsd.org References: rt-ticket-190...@tracker2.aebc.com 20090121063945.784f71065...@hub.freebsd.org Message-ID: rt-3.8.2-24799-1232519921-72.190335-...@tracker2.aebc.com Precedence: bulk X-RT-Loop-Prevention: tracker2.aebc.com RT-Ticket: tracker2.aebc.com #190335 Managed-by: RT 3.8.2 (http://www.bestpractical.com/rt/) RT-Originator: freebsd-questions@freebsd.org Auto-Submitted: auto-replied To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-RT-Original-Encoding: utf-8 Date: Tue, 20 Jan 2009 22:38:41 -0800 Subject: [Trouble Ticket #190335] AutoReply: freebsd-questions Digest, Vol 246, Issue 26 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Reply-To: supp...@aebc.com List-Id: User questions freebsd-questions.freebsd.org List-Unsubscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions, mailto:freebsd-questions-requ...@freebsd.org?subject=unsubscribe List-Archive: http://lists.freebsd.org/pipermail/freebsd-questions List-Post: mailto:freebsd-questions@freebsd.org List-Help: mailto:freebsd-questions-requ...@freebsd.org?subject=help List-Subscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions, mailto:freebsd-questions-requ...@freebsd.org?subject=subscribe Sender: owner-freebsd-questi...@freebsd.org Errors-To: owner-freebsd-questi...@freebsd.org Thank you for contacting us. This message has been automatically generated in response to the creation of a trouble ticket regarding: freebsd-questions Digest, Vol 246, Issue 26, a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Trouble Ticket #190335]. Please include the string: [Trouble Ticket #190335] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, supp...@aebc.com - Send freebsd-questions mailing list submissions to freebsd-questions@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-questions or, via email, send a message with subject or body 'help' to
[SpamCop (66.51.128.45) id:3804161254][Trouble Ticket #190335] AutoReply: freebsd-questi..
[ SpamCop V2 ] This message is brief for your comfort. Please use links below for details. Unsolicited bounce from: 66.51.128.45 http://www.spamcop.net/w3m?i=z3804161254zb8f468ed2448a38597aa31de0ddbe41cz 66.51.128.45 appears to be sending unsolicited bounces, please see: http://www.spamcop.net/fom-serve/cache/329.html [ Offending message ] X-Claws-Bogosity: Ham, spamicity=0 [whitelisted] X-Apparently-To: ges...@yahoo.com via 68.142.207.115; Tue, 20 Jan 2009 22:41:07 -0800 X-YMailISG: .Dv8j18WLDtuJNxtWLhDpf5mpeWFUghNdv_egb_0fiZXg1RCIX735NHbTO4clF89wN6gneANUXqOut8aaecrNre7XPBoTfchA4NFlU0TRJqOCLU_mg0l5Z0_qbqu8xMJfpRn3An.qvcED777FwkCZQVEXN5Qa0vSW3Nm5cqisI_itxdD2dWcDmVt0oPwAE87AbDClIGtYWvkHHwS2kDGt_cGFpaZnbBIkxYHVXnWFcg8F8XH6v3K1DET2NtH5Am8wwm9un5sIVnxKYalYMlU7HHXa1itu7PXH7LbJRG3by.ydjpQN7TXysv8lExiTgdk4Kczs69igNPnXubTNINHACSpnufW_Sw- X-Originating-IP: [69.147.83.53] Authentication-Results: mta324.mail.re4.yahoo.com from=freebsd.org; domainkeys=neutral (no sig) Received: from 69.147.83.53 (EHLO mx2.freebsd.org) (69.147.83.53) by mta324.mail.re4.yahoo.com with SMTP; Tue, 20 Jan 2009 22:41:06 -0800 Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 8968B15F523; Wed, 21 Jan 2009 06:40:24 + (UTC) (envelope-from owner-freebsd-questi...@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 755D71065694; Wed, 21 Jan 2009 06:40:24 + (UTC) (envelope-from owner-freebsd-questi...@freebsd.org) Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B8901065676 for freebsd-questions@freebsd.org; Wed, 21 Jan 2009 06:40:06 + (UTC) (envelope-from apa...@tracker2.aebc.com) Received: from tracker2.aebc.com (xx6651128045.cipherkey.com [66.51.128.45]) by mx1.freebsd.org (Postfix) with ESMTP id 088C88FC34 for freebsd-questions@freebsd.org; Wed, 21 Jan 2009 06:40:05 + (UTC) (envelope-from apa...@tracker2.aebc.com) Received: from tracker2.aebc.com (localhost.localdomain [127.0.0.1]) by tracker2.aebc.com (Postfix) with ESMTP id AFD4D6768C8 for freebsd-questions@freebsd.org; Tue, 20 Jan 2009 22:38:41 -0800 (PST) Received: (from apa...@localhost) by tracker2.aebc.com (8.13.8/8.13.8/Submit) id n0L6cfin026492; Tue, 20 Jan 2009 22:38:41 -0800 From: AEBC Support via RT supp...@aebc.com In-Reply-To: 20090121063945.784f71065...@hub.freebsd.org References: rt-ticket-190...@tracker2.aebc.com 20090121063945.784f71065...@hub.freebsd.org Message-ID: rt-3.8.2-24799-1232519921-72.190335-...@tracker2.aebc.com Precedence: bulk X-RT-Loop-Prevention: tracker2.aebc.com RT-Ticket: tracker2.aebc.com #190335 Managed-by: RT 3.8.2 (http://www.bestpractical.com/rt/) RT-Originator: freebsd-questions@freebsd.org Auto-Submitted: auto-replied To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-RT-Original-Encoding: utf-8 Date: Tue, 20 Jan 2009 22:38:41 -0800 Subject: [Trouble Ticket #190335] AutoReply: freebsd-questions Digest, Vol 246, Issue 26 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Reply-To: supp...@aebc.com List-Id: User questions freebsd-questions.freebsd.org List-Unsubscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions, mailto:freebsd-questions-requ...@freebsd.org?subject=unsubscribe List-Archive: http://lists.freebsd.org/pipermail/freebsd-questions List-Post: mailto:freebsd-questions@freebsd.org List-Help: mailto:freebsd-questions-requ...@freebsd.org?subject=help List-Subscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions, mailto:freebsd-questions-requ...@freebsd.org?subject=subscribe Sender: owner-freebsd-questi...@freebsd.org Errors-To: owner-freebsd-questi...@freebsd.org Thank you for contacting us. This message has been automatically generated in response to the creation of a trouble ticket regarding: freebsd-questions Digest, Vol 246, Issue 26, a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Trouble Ticket #190335]. Please include the string: [Trouble Ticket #190335] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, supp...@aebc.com - Send freebsd-questions mailing list submissions to freebsd-questions@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-questions or, via email, send a message with subject or body 'help' to
[SpamCop (66.51.128.45) id:3804161333][Trouble Ticket #190335] AutoReply: freebsd-questi..
[ SpamCop V2 ] This message is brief for your comfort. Please use links below for details. Unsolicited bounce from: 66.51.128.45 http://www.spamcop.net/w3m?i=z3804161333za50641095fcb00ec353c1b57da3d7a11z 66.51.128.45 appears to be sending unsolicited bounces, please see: http://www.spamcop.net/fom-serve/cache/329.html [ Offending message ] X-Claws-Bogosity: Ham, spamicity=0 [whitelisted] X-Apparently-To: ges...@yahoo.com via 68.142.207.115; Tue, 20 Jan 2009 22:41:07 -0800 X-YMailISG: .Dv8j18WLDtuJNxtWLhDpf5mpeWFUghNdv_egb_0fiZXg1RCIX735NHbTO4clF89wN6gneANUXqOut8aaecrNre7XPBoTfchA4NFlU0TRJqOCLU_mg0l5Z0_qbqu8xMJfpRn3An.qvcED777FwkCZQVEXN5Qa0vSW3Nm5cqisI_itxdD2dWcDmVt0oPwAE87AbDClIGtYWvkHHwS2kDGt_cGFpaZnbBIkxYHVXnWFcg8F8XH6v3K1DET2NtH5Am8wwm9un5sIVnxKYalYMlU7HHXa1itu7PXH7LbJRG3by.ydjpQN7TXysv8lExiTgdk4Kczs69igNPnXubTNINHACSpnufW_Sw- X-Originating-IP: [69.147.83.53] Authentication-Results: mta324.mail.re4.yahoo.com from=freebsd.org; domainkeys=neutral (no sig) Received: from 69.147.83.53 (EHLO mx2.freebsd.org) (69.147.83.53) by mta324.mail.re4.yahoo.com with SMTP; Tue, 20 Jan 2009 22:41:06 -0800 Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 8968B15F523; Wed, 21 Jan 2009 06:40:24 + (UTC) (envelope-from owner-freebsd-questi...@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 755D71065694; Wed, 21 Jan 2009 06:40:24 + (UTC) (envelope-from owner-freebsd-questi...@freebsd.org) Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B8901065676 for freebsd-questions@freebsd.org; Wed, 21 Jan 2009 06:40:06 + (UTC) (envelope-from apa...@tracker2.aebc.com) Received: from tracker2.aebc.com (xx6651128045.cipherkey.com [66.51.128.45]) by mx1.freebsd.org (Postfix) with ESMTP id 088C88FC34 for freebsd-questions@freebsd.org; Wed, 21 Jan 2009 06:40:05 + (UTC) (envelope-from apa...@tracker2.aebc.com) Received: from tracker2.aebc.com (localhost.localdomain [127.0.0.1]) by tracker2.aebc.com (Postfix) with ESMTP id AFD4D6768C8 for freebsd-questions@freebsd.org; Tue, 20 Jan 2009 22:38:41 -0800 (PST) Received: (from apa...@localhost) by tracker2.aebc.com (8.13.8/8.13.8/Submit) id n0L6cfin026492; Tue, 20 Jan 2009 22:38:41 -0800 From: AEBC Support via RT supp...@aebc.com In-Reply-To: 20090121063945.784f71065...@hub.freebsd.org References: rt-ticket-190...@tracker2.aebc.com 20090121063945.784f71065...@hub.freebsd.org Message-ID: rt-3.8.2-24799-1232519921-72.190335-...@tracker2.aebc.com Precedence: bulk X-RT-Loop-Prevention: tracker2.aebc.com RT-Ticket: tracker2.aebc.com #190335 Managed-by: RT 3.8.2 (http://www.bestpractical.com/rt/) RT-Originator: freebsd-questions@freebsd.org Auto-Submitted: auto-replied To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-RT-Original-Encoding: utf-8 Date: Tue, 20 Jan 2009 22:38:41 -0800 Subject: [Trouble Ticket #190335] AutoReply: freebsd-questions Digest, Vol 246, Issue 26 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Reply-To: supp...@aebc.com List-Id: User questions freebsd-questions.freebsd.org List-Unsubscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions, mailto:freebsd-questions-requ...@freebsd.org?subject=unsubscribe List-Archive: http://lists.freebsd.org/pipermail/freebsd-questions List-Post: mailto:freebsd-questions@freebsd.org List-Help: mailto:freebsd-questions-requ...@freebsd.org?subject=help List-Subscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions, mailto:freebsd-questions-requ...@freebsd.org?subject=subscribe Sender: owner-freebsd-questi...@freebsd.org Errors-To: owner-freebsd-questi...@freebsd.org Thank you for contacting us. This message has been automatically generated in response to the creation of a trouble ticket regarding: freebsd-questions Digest, Vol 246, Issue 26, a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Trouble Ticket #190335]. Please include the string: [Trouble Ticket #190335] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, supp...@aebc.com - Send freebsd-questions mailing list submissions to freebsd-questions@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-questions or, via email, send a message with subject or body 'help' to
UFS2 limits
Hi, I have a FreeBSD server that has about 10,500 subdirectories within a single directory. This number will keep rising and I assume UFS2 has a limit to the number of sub-directories in a single directory - can anyone tell me what it is? What about ZFS? At some point I'll have to re-arrange things so that I have a deeper directory structure, just wondering when I'll hit the limit so I can plan in advance :-) Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
gcc linking: undefined reference to '__gnu_norm::...' ?
Hello, I'm using FreeBSD 5.3-Stable. I'm compiling a package from sources myself (it's the most recent LyX software). The compilation goes almost fine, only at the final linking it gives strange errors. A zillion lines, that all share having a problem with __gnu_norm:: The LyX mailing list seems to have only Linux users, and my problem is unknown there. So I guessed it is a specific FreeBSD issue. Does somebody have an idea what's going wrong here: - $ gmake [many compilation lines] g++ -g -O -fno-exceptions -o lyx-xforms main.o Bidi.o [...] trans_mgr.o undo.o vc-backend.o version.o vspace.o [...] -lICE -laspell -lm -L/usr/X11R6/lib -lX11 -lz BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE9_M_insertENS_14_List_iteratorIS1_EERKS1_+0x19): In function `__gnu_norm::listBranch, std::allocatorBranch ::_M_insert(__gnu_norm::_List_iteratorBranch, Branch const)': /usr/include/c++/3.4/bits/locale_facets.tcc:2443: undefined reference to `__gnu_norm::_List_node_base::hook(__gnu_norm::_List_node_base*)' BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE8_M_eraseENS_14_List_iteratorIS1_EE+0xd): In function `__gnu_norm::listBranch, std::allocatorBranch ::_M_erase(__gnu_norm::_List_iteratorBranch)': [...and a zillion more of such lines...] Thanks, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to query date of when package was installed?
Hi, I know I can query the package list on before/after date with pkg_glob. But how do I query simply the package date of when it was installed. For example something like: gimp-2.2.2,1 17-01-2005 16:05:20 Rob. __ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Protecting SSH from brute force attacks
Vulpes Velox wrote: On Thu, 7 Oct 2004 15:15:25 -0700 (PDT) Luke [EMAIL PROTECTED] wrote: There are several script kiddies out there hitting my SSH server every day. Sometimes they attempt to brute-force their way in man login.conf for more info :) I'm just guessing, but are you trying to tell me that login-retries in login.conf is useful? I have tried that by setting it to 2, but it seems to have no effect on the sshd login behaviour. I always can try the password 6 times: $ ssh [EMAIL PROTECTED] Password: Password: Password: [EMAIL PROTECTED]'s password: Permission denied, please try again. [EMAIL PROTECTED]'s password: Permission denied, please try again. [EMAIL PROTECTED]'s password: Permission denied (publickey,password,keyboard-interactive). $ So could you be a little more specific as to where login.conf is of help here? Thanks, Rob. ___ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ipfw divert but no packet payload?
I've followed the divert and ipfw manpages, Stevens _Unix Network Programming_ etc, Baldine's Feb 2000 Divert Sockets mini-HOWTO at www.tldp.org/HOWTO, and everything else I could find (not very much exactly about this, tho). My situation is: firewall: have ipfw divert portnum rule for port 80 out user program: recvfrom() on a raw socket bound to portnum My question is: whether I should expect to be able to get the full packet including data payload for a packet diverted to port portnum ? I want to be able to inspect the packet content before it is sent out. Right now my user code just prints the packet, then does sendto() back to the raw socket to send the packet on its way, but there is no data payload. Everything I've seen about divert seems clearly to expect the full data payload to be available to whatever is receiving from the raw socket. Web browsing works, tcpdump shows full packets, but I can't see any data payload in the user program. User prog can read the ip header length, tcp header length, and full ip packet length from the packet (20, 40, and 60 respectively, after converting to bytes). Per the 60, packet seems to be saying there *isn't* any data payload, only the 20+40 header bytes. The recvfrom() memory buffer argument is 2048 bytes long, and I can printout all its many 0 bytes after the headers. I understand tcpdump uses the bsd packet filter to get merely a copy of the packet, but the full packets are getting to where they're addressed somehow because browsing is working, and tcpdump is showing packet sizes like 467, etc. ipfw -a list shows the same divert packet count as how many my user program sees, and byte count == (60 * pkt count). (Tho a couple of early runs, before I did full printouts and had settled on simple ipfw rules, had occasional 44 byte recvfrom() returns and ipfw packet sizes mixed in with the 60 byte returns/sizes.) Any suggestions would be very appreciated. (I'm using FreeBSD as Mac OSX 10.2.8, which has shown no strangeness other than a couple of odd console.log alerts relating to unrecognized ipfw rules while I was fiddling with my own ipfw preparing for trying the divert stuff.) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ipfw divert but no packet payload?
Here's the ipfw -a list content at the start. I run a shell script manually to set these, it starts with a flush then adds rules. The keep-state are leftover from studying dynamic rule creation. (FWIW, Mac OSX 10.2.8 seemed on brief review not to use a 3000 check-state I originally was trying.) 2000 - 2040 are stock OSX, 4010 - 4030 are mine, 4040 - end are stock OSX. -- 02000 allow ip from any to any via lo* 02010 deny ip from 127.0.0.0/8 to any in 02020 deny ip from any to 127.0.0.0/8 in 02030 deny ip from 224.0.0.0/3 to any in 02040 deny tcp from any to 224.0.0.0/3 in 04010 allow udp from me to any 53 keep-state out 04020 divert 55374 tcp from me to any 80 out 04030 allow tcp from me to any keep-state out setup 04040 allow tcp from any to any established 12190 deny tcp from any to any 65535 allow ip from any to any -- On Wed, 12 May 2004, JJB wrote: Post you ipfw rules so people can see what you are talking about. -Original Message- I've followed the divert and ipfw manpages, Stevens _Unix Network Programming_ etc, Baldine's Feb 2000 Divert Sockets mini-HOWTO at www.tldp.org/HOWTO, and everything else I could find (not very much exactly about this, tho). My situation is: firewall: have ipfw divert portnum rule for port 80 out user program: recvfrom() on a raw socket bound to portnum My question is: whether I should expect to be able to get the full packet including data payload for a packet diverted to port portnum ? I want to be able to inspect the packet content before it is sent out. Right now my user code just prints the packet, then does sendto() back to the raw socket to send the packet on its way, but there is no data payload. Everything I've seen about divert seems clearly to expect the full data payload to be available to whatever is receiving from the raw socket. Web browsing works, tcpdump shows full packets, but I can't see any data payload in the user program. User prog can read the ip header length, tcp header length, and full ip packet length from the packet (20, 40, and 60 respectively, after converting to bytes). Per the 60, packet seems to be saying there *isn't* any data payload, only the 20+40 header bytes. The recvfrom() memory buffer argument is 2048 bytes long, and I can printout all its many 0 bytes after the headers. I understand tcpdump uses the bsd packet filter to get merely a copy of the packet, but the full packets are getting to where they're addressed somehow because browsing is working, and tcpdump is showing packet sizes like 467, etc. ipfw -a list shows the same divert packet count as how many my user program sees, and byte count == (60 * pkt count). (Tho a couple of early runs, before I did full printouts and had settled on simple ipfw rules, had occasional 44 byte recvfrom() returns and ipfw packet sizes mixed in with the 60 byte returns/sizes.) Any suggestions would be very appreciated. (I'm using FreeBSD as Mac OSX 10.2.8, which has shown no strangeness other than a couple of odd console.log alerts relating to unrecognized ipfw rules while I was fiddling with my own ipfw preparing for trying the divert stuff.) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
