c++11 question: clang++ 3.3 header not found

2013-08-27 Thread Quark 
% uname -a
FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC 2013 
    r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

% clang++ --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd9.2
Thread model: posix

test program
#include 
#include 

int main( int argc, char* argv[])
{
        auto f = std::async( [] () {
                        std::cout << "Hello, World!" << std::endl;
                        });
        f.wait();
        return 0;
}


error received is
% clang++ -otest test.cc

test.cc:2:10: fatal error: 'future' file not found
#include 
         ^
1 error generated.

I guess clang is re-using system headers which belong to older gcc 4.2
I also have gcc48 installed, how can I make clang to refer gcc48 headers?
___
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"

clang and c++11 question

2013-08-27 Thread Quark 
% uname -a
FreeBSD cobalt.corp.nai.org 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 
20:25:04 UTC 2013     r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  
amd64


% clang++ --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd9.2
Thread model: posix

clang 3.3 is C++11 feature complete, but it fails to find  and/or 
 headers.
since it is looking in system compiler path, which is old gcc4.2, not C++11 
ready

how to make clang refer headers from gcc48's installation( via pkg_add)?
___
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"

c++11 and clang question

2013-08-27 Thread Quark 
% uname -a
FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC 2013 
    r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

% clang++ --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd9.2
Thread model: posix

// test.cc
#include 
#include 

int main( int argc, char* argv[])
{
        auto f = std::async( [] () {
                        std::cout << "Hello, World!" << std::endl;
                        });
        f.wait();
        return 0;
}

% clang++ -v -otest test.cc
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: x86_64-unknown-freebsd9.2
Thread model: posix
 "/usr/bin/clang++" -cc1 -triple x86_64-unknown-freebsd9.2 -emit-obj 
-mrelax-all -disable-free -main-file-name test.cc -mrelocation-model static 
-mdisable-fp-elim -masm-verbose -mconstructor-aliases -munwind-tables 
-target-cpu x86-64 -v -resource-dir /usr/bin/../lib/clang/3.3 
-fdeprecated-macro -fdebug-compilation-dir /home/mshaikh -ferror-limit 19 
-fmessage-length 168 -mstackrealign -fobjc-runtime=gnustep 
-fobjc-default-synthesize-properties -fcxx-exceptions -fexceptions 
-fdiagnostics-show-option -fcolor-diagnostics -backend-option -vectorize-loops 
-o /tmp/test-jIvr1p.o -x c++ test.cc
clang -cc1 version 3.3 based upon LLVM 3.3 default target 
x86_64-unknown-freebsd9.2
ignoring nonexistent directory "/usr/include/c++/4.2/backward/backward"
ignoring nonexistent directory "/usr/bin/../lib/clang/3.3/include"
ignoring duplicate directory "/usr/include/c++/4.2"
ignoring duplicate directory "/usr/include/c++/4.2/backward"
ignoring duplicate directory "/usr/include/c++/4.2/backward"
#include "..." search starts here:
#include <...> search starts here:
 /usr/include/c++/4.2
 /usr/include/c++/4.2/backward
 /usr/include/clang/3.3
 /usr/include
End of search list.
test.cc:2:10: fatal error: 'future' file not found
#include 
         ^
1 error generated.

clang is re-using system headers which belong to older gcc 4.2
Can clang be educated to refer gcc48 headers, installed via pkg_add?
___
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: c++11 question: clang++ 3.3 header not found

2013-08-27 Thread Quark 
list, please pardon
my stupid mail client hung, giving me impression that e-mail was not sent.
apologies for spam.


- Original Message -
> From: Quark 
> To: "freebsd-questions@freebsd.org" 
> Cc: 
> Sent: Tuesday, 27 August 2013 12:52 PM
> Subject: c++11 question: clang++ 3.3  header not found
> 
> % uname -a
> FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC 
> 2013 
>     r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> % clang++ --version
> FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
> Target: x86_64-unknown-freebsd9.2
> Thread model: posix
> 
> test program
> #include 
> #include 
> 
> int main( int argc, char* argv[])
> {
>         auto f = std::async( [] () {
>                         std::cout << "Hello, World!" << 
> std::endl;
>                         });
>         f.wait();
>         return 0;
> }
> 
> 
> error received is
> % clang++ -otest test.cc
> 
> test.cc:2:10: fatal error: 'future' file not found
> #include 
>          ^
> 1 error generated.
> 
> I guess clang is re-using system headers which belong to older gcc 4.2
> I also have gcc48 installed, how can I make clang to refer gcc48 headers?
> ___
> 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"
> 
___
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: c++11 question: clang++ 3.3 header not found

2013-08-27 Thread Tijl Coosemans 
On Tue, 27 Aug 2013 15:22:49 +0800 (SGT) Quark wrote:
> % uname -a
> FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC 
> 2013     r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> % clang++ --version
> FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
> Target: x86_64-unknown-freebsd9.2
> Thread model: posix
> 
> test program
> #include 
> #include 
> 
> int main( int argc, char* argv[])
> {
>         auto f = std::async( [] () {
>                         std::cout << "Hello, World!" << std::endl;
>                         });
>         f.wait();
>         return 0;
> }
> 
> 
> error received is
> % clang++ -otest test.cc
> 
> test.cc:2:10: fatal error: 'future' file not found
> #include 
>          ^
> 1 error generated.
> 
> I guess clang is re-using system headers which belong to older gcc 4.2
> I also have gcc48 installed, how can I make clang to refer gcc48 headers?

There two C++ runtime libraries, the old gcc libstdc++ which is used by
default and the new C++11 libc++.  You can use the latter like this:

clang++ -std=c++11 -stdlib=libc++ -otest test.cc


signature.asc
Description: PGP signature

Fwd: c++11 question: clang++ 3.3 header not found

2013-08-27 Thread Константин Беседин 
AFAIK, the easiest way to get C++11 support in clang is to use libc++ (see
http://blogs.freebsdish.org/theraven/2013/01/03/the-new-c-stack-in-9-1/).
See also
https://lists.freebsd.org/pipermail/freebsd-toolchain/2013-May/000841.html .


2013/8/27 Quark 

> % uname -a
> FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC
> 2013 r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
>
> % clang++ --version
> FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
> Target: x86_64-unknown-freebsd9.2
> Thread model: posix
>
> test program
> #include 
> #include 
>
> int main( int argc, char* argv[])
> {
> auto f = std::async( [] () {
> std::cout << "Hello, World!" << std::endl;
> });
> f.wait();
> return 0;
> }
>
>
> error received is
> % clang++ -otest test.cc
>
> test.cc:2:10: fatal error: 'future' file not found
> #include 
>  ^
> 1 error generated.
>
> I guess clang is re-using system headers which belong to older gcc 4.2
> I also have gcc48 installed, how can I make clang to refer gcc48 headers?
> ___
> 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"
>
___
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: c++11 question: clang++ 3.3 header not found

2013-08-27 Thread Quark 




- Original Message -
> From: Tijl Coosemans 
> To: Quark 
> Cc: "freebsd-questions@freebsd.org" 
> Sent: Tuesday, 27 August 2013 1:41 PM
> Subject: Re: c++11 question: clang++ 3.3  header not found
> 
> On Tue, 27 Aug 2013 15:22:49 +0800 (SGT) Quark wrote:
>>  % uname -a
>>  FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC 
> 2013     r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
>> 
>>  % clang++ --version
>>  FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
>>  Target: x86_64-unknown-freebsd9.2
>>  Thread model: posix
>> 
>>  test program
>>  #include 
>>  #include 
>> 
>>  int main( int argc, char* argv[])
>>  {
>>          auto f = std::async( [] () {
>>                          std::cout << "Hello, World!" 
> << std::endl;
>>                          });
>>          f.wait();
>>          return 0;
>>  }
>> 
>> 
>>  error received is
>>  % clang++ -otest test.cc
>> 
>>  test.cc:2:10: fatal error: 'future' file not found
>>  #include 
>>           ^
>>  1 error generated.
>> 
>>  I guess clang is re-using system headers which belong to older gcc 4.2
>>  I also have gcc48 installed, how can I make clang to refer gcc48 headers?
> 
> There two C++ runtime libraries, the old gcc libstdc++ which is used by
> default and the new C++11 libc++.  You can use the latter like this:
> 
> clang++ -std=c++11 -stdlib=libc++ -otest test.cc
> 

thanks, it worked.
___
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"

CURDIR-relative paths in ports' Makefiles

2013-08-27 Thread Koslov Sergey 

Hello

I've noticed that many ports are using ${.CURDIR}/../../some/port 
construction in their Makefiles.


But if you copy on of these ports elsewhere it won't work as expected 
because of the relative path.

Shouldn't they use ${PORTSDIR}/some/port instead?

Thanks for the replies.

Kozlov Sergey
___
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"

TEMPer1 on FreeBSD

2013-08-27 Thread TJ 

Hi guys,
I have just purchased a TEMPer1 for monitoring the temperature of our rack.
I have been looking at way of getting this working as the default 
drivers pick it up as a keyboard and mouse.


Aug 27 12:13:41 test-1 kernel: ukbd0: 2.00/0.01, addr 2> on usbus1

Aug 27 12:13:41 test-1 kernel: kbd2 at ukbd0
Aug 27 12:13:41 test-1 kernel: ums0: 2.00/0.01, addr 2> on usbus1


I have been looking at UTHUM 
 but i 
think that is only for OpenBSD as cannot see any mention of it the src 
or loader.conf


I have also looked at this  and this 
 With no joy.

I think both of those are designed to run on the TEMPer but not the TEMPer1.

Even with the uchcom(8) driver kldload into the kernel i cannot get it 
working.


Can anyone help with this?
___
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: CURDIR-relative paths in ports' Makefiles

2013-08-27 Thread Matthew Seaman 
On 27/08/2013 13:04, Koslov Sergey wrote:
> Hello
> 
> I've noticed that many ports are using ${.CURDIR}/../../some/port
> construction in their Makefiles.
> 
> But if you copy on of these ports elsewhere it won't work as expected
> because of the relative path.
> Shouldn't they use ${PORTSDIR}/some/port instead?

The use of relative paths is taken straight from The Porter's Handbook.  eg.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-masterdir.html

So it's officially correct to do that.

While there is no direct proscription against saying
${PORTSDIR}/some/port in that circumstance that I can see in the
documentation, relative paths are generally only used in slave ports for
the ${MASTERDIR} setting or more generally for including other
Makefiles; whereas absolute paths are used for all sorts of FOO_DEPENDS
variables.  A quick (and by no means  definitive) grepping of the ports
tree I just did hasn't shown up any counter examples.

If you intend to copy a slave port to some other location in your
filesystem and have it refer to the original master port within the
default ports tree, then you're assumed to be capable of editing the
Makefile to resolve any such changes.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature

Re: Way to be announced about security updates and new releases

2013-08-27 Thread Zyumbilev, Peter 
http://www.freebsd.org/security/rss.xml

?
Peter

On 21/08/2013 09:54, Antonio Kless wrote:
> Is there any way to be noticed, when security updates or new releases are
> available?
> 
> https://twitter.com/freebsd nearly would be a solution, if it did not
> repostquestions from its
> subscribers and other information that is not related to updates.
> 
___
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"

Fatal trap 12 after upgrading from 8.2 to 8.4

2013-08-27 Thread Patrick 
I've got a system running on a VPS that I'm trying to upgrade from 8.2
to 8.4. It has a ZFS root. After booting the new kernel, I get:

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x40
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x810d7691
stack pointer   = 0x28:0xff81ba60
frame pointer   = 0x28:0xff81ba90
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1 (kernel)
trap number = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0x8066cb96 at kdb_backtrace+0x66
#1 0x8063925e at panic+0x1ce
#2 0x809c21d0 at trap_fatal+0x290
#3 0x809c255e at trap_pfault+0x23e
#4 0x809c2a2e at trap+0x3ce
#5 0x809a9624 at calltrap+0x8
#6 0x810df517 at vdev_mirror_child_select+0x67
#7 0x810dfacc at vdev_mirror_io_start+0x24c
#8 0x810f7c52 at zio_vdev_io_start+0x232
#9 0x810f76f3 at zio_execute+0xc3
#10 0x810f77ad at zio_wait+0x2d
#11 0x8108991e at arc_read+0x6ce
#12 0x8109d9d4 at dmu_objset_open_impl+0xd4
#13 0x810b4014 at dsl_pool_init+0x34
#14 0x810c7eea at spa_load+0x6aa
#15 0x810c90b2 at spa_load_best+0x52
#16 0x810cb0ca at spa_open_common+0x14a
#17 0x810a892d at dsl_dir_open_spa+0x2cd
Uptime: 3s
Cannot dump. Device not defined or unavailable.

I've booted back into the 8.2 kernel without any problems, but I'm
wondering if anyone can suggest what I should try to get this working?
I used freebsd-update to upgrade, and this was after the first
"freebsd-update install" where it installs the kernel.

My /boot/loader.conf has:

zfs_load="YES"
vfs.root.mountfrom="zfs:zroot"

Patrick
___
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: f9 snmpd[4517]: stack overflow detected; terminated

2013-08-27 Thread alexus 
snmpd.config is standard

[alexus@f9 ~]$ head -1 /etc/snmpd.config
# $FreeBSD: release/9.1.0/etc/snmpd.config 216595 2010-12-20 17:28:15Z
syrinx $
[alexus@f9 ~]$



On Mon, Aug 26, 2013 at 11:03 PM, alexus  wrote:

> f9# gdb `which bsnmpd` /bsnmpd.core
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols
> found)...
> Core was generated by `bsnmpd'.
> Program terminated with signal 6, Aborted.
> Reading symbols from /lib/libbegemot.so.4...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libbegemot.so.4
> Reading symbols from /usr/lib/libbsnmp.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libbsnmp.so.6
> Reading symbols from /usr/lib/libwrap.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libwrap.so.6
> Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done.
> Loaded symbols for /lib/libc.so.7
> Reading symbols from /lib/libcrypto.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libcrypto.so.6
> Reading symbols from /usr/lib/snmp_mibII.so...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/snmp_mibII.so
> Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols
> found)...done.
> Loaded symbols for /libexec/ld-elf.so.1
> #0  0x000800f54d6c in kill () from /lib/libc.so.7
> (gdb)
>
>
>
> On Mon, Aug 26, 2013 at 10:42 PM, James Gosnell wrote:
>
>> What's the core dump and your config file look like?
>>
>>
>> On Mon, Aug 26, 2013 at 9:28 PM, alexus  wrote:
>>
>> > My bsnmpd(1) keep crashing(
>> >
>> > f9# uname -a
>> > FreeBSD f9.alexus.org 9.1-RELEASE-p6 FreeBSD 9.1-RELEASE-p6 #0: Wed
>> Aug 21
>> > 20:40:52 UTC 2013
>> > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>> >  amd64
>> > f9# bzip2 -cd all.log.1.bz2 | grep snmpd
>> > Aug 24 20:59:55 f9 snmpd[4517]: stack overflow detected; terminated
>> > Aug 24 20:59:55 f9 kernel: Aug 24 20:59:55 f9 snmpd[4517]: stack
>> overflow
>> > detected; terminated
>> > Aug 24 20:59:56 f9 kernel: pid 4517 (bsnmpd), uid 0: exited on signal 6
>> > (core dumped)
>> > f9# head -1 /etc/snmpd.config
>> > # $FreeBSD: release/9.1.0/etc/snmpd.config 216595 2010-12-20 17:28:15Z
>> > syrinx $
>> > f9#
>> >
>> > What can I do to resolve it?
>> >
>> > --
>> > http://alexus.org/
>> > ___
>> > 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"
>> >
>>
>>
>>
>> --
>> James Gosnell, ACP
>> ___
>> 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"
>>
>
>
>
> --
> http://alexus.org/
>



-- 
http://alexus.org/
___
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"

Jail with public IP alias

2013-08-27 Thread Alejandro Imass 
Hi,

I have a machine with several public IPs on the same NIC and I bound
one of those IPs to a jail created with EzJail. Suppose the scenario
is something like this:

em0
190.100.100.1
190.100.100.2
190.100.100.3
190.100.100.4

In the jail we are bound only to 190.100.100.4

The default router is correctly set on the jail, etc.

But when we ssh out of that jail, or send an email, the receiving end
always sees 190.100.100.1 not 190.100.100.4 which is the IP the jail
is bound to.

Since I can't use traceroute or netstat I can only guess that it's
using the base systems routing table for link#1 and that's why it's
always going out of the first IP of that NIC.

Is there any way to fix this? Besides adding another NIC which we
currently can't do.

Thanks,

-- 
Alejandro Imass
___
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: f9 snmpd[4517]: stack overflow detected; terminated

2013-08-27 Thread Fernando Apesteguía 
El 27/08/2013 05:03, "alexus"  escribió:
>
> f9# gdb `which bsnmpd` /bsnmpd.core
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
details.
> This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols
> found)...
> Core was generated by `bsnmpd'.
> Program terminated with signal 6, Aborted.
> Reading symbols from /lib/libbegemot.so.4...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libbegemot.so.4
> Reading symbols from /usr/lib/libbsnmp.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libbsnmp.so.6
> Reading symbols from /usr/lib/libwrap.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libwrap.so.6
> Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done.
> Loaded symbols for /lib/libc.so.7
> Reading symbols from /lib/libcrypto.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libcrypto.so.6
> Reading symbols from /usr/lib/snmp_mibII.so...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/snmp_mibII.so
> Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols
> found)...done.
> Loaded symbols for /libexec/ld-elf.so.1
> #0  0x000800f54d6c in kill () from /lib/libc.so.7
> (gdb)

Is that the whole backtrace?

>
>
>
> On Mon, Aug 26, 2013 at 10:42 PM, James Gosnell wrote:
>
> > What's the core dump and your config file look like?
> >
> >
> > On Mon, Aug 26, 2013 at 9:28 PM, alexus  wrote:
> >
> > > My bsnmpd(1) keep crashing(
> > >
> > > f9# uname -a
> > > FreeBSD f9.alexus.org 9.1-RELEASE-p6 FreeBSD 9.1-RELEASE-p6 #0: Wed
Aug
> > 21
> > > 20:40:52 UTC 2013
> > > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
> > >  amd64
> > > f9# bzip2 -cd all.log.1.bz2 | grep snmpd
> > > Aug 24 20:59:55 f9 snmpd[4517]: stack overflow detected; terminated
> > > Aug 24 20:59:55 f9 kernel: Aug 24 20:59:55 f9 snmpd[4517]: stack
overflow
> > > detected; terminated
> > > Aug 24 20:59:56 f9 kernel: pid 4517 (bsnmpd), uid 0: exited on signal
6
> > > (core dumped)
> > > f9# head -1 /etc/snmpd.config
> > > # $FreeBSD: release/9.1.0/etc/snmpd.config 216595 2010-12-20 17:28:15Z
> > > syrinx $
> > > f9#
> > >
> > > What can I do to resolve it?
> > >
> > > --
> > > http://alexus.org/
> > > ___
> > > 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"
> > >
> >
> >
> >
> > --
> > James Gosnell, ACP
> > ___
> > 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"
> >
>
>
>
> --
> http://alexus.org/
> ___
> 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"
___
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: Jail with public IP alias

2013-08-27 Thread Alejandro Imass 
On Tue, Aug 27, 2013 at 4:59 PM, Alejandro Imass  wrote:
> Hi,
>
> I have a machine with several public IPs on the same NIC and I bound
> one of those IPs to a jail created with EzJail. Suppose the scenario
> is something like this:
>
> em0
> 190.100.100.1
> 190.100.100.2
> 190.100.100.3
> 190.100.100.4
>
> In the jail we are bound only to 190.100.100.4
>
> The default router is correctly set on the jail, etc.
>
> But when we ssh out of that jail, or send an email, the receiving end
> always sees 190.100.100.1 not 190.100.100.4 which is the IP the jail
> is bound to.


I think my problem is actually more basic than this. The problem
actually occurs on the base system as well and I think it's because
all the IPs are on the same subnet, then the kernel assumes to use the
primary IP as the source address. For the sake and usefulness of the
mail archives I will end this thread here and start another one with a
more appropriate title, not before researching to see if this can be
done with the routing table or if I need to use ipfw to re-write the
source address.

Thanks,

-- 
Alejandro Imass
___
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: Jail with public IP alias

2013-08-27 Thread Patrick 
That's not the behaviour I see. My jail has a private and public IP.

$ ifconfig bce1
bce1: flags=8843 metric 0 mtu 1500

options=c01bb
ether a4:ba:db:29:7a:1b
inet 192.168.42.23 netmask 0x broadcast 192.168.42.23
media: Ethernet autoselect (1000baseT )
status: active

If I ssh into another host on the 192.168.42.0 network, I see:

$ who
patrick  ttyp1Aug 27 15:21 (192.168.42.23)

The host of the jail has multiple IPs on that private subnet:

$ ifconfig bce1
bce1: flags=8843 metric 0 mtu 1500

options=c01bb
ether a4:ba:db:29:7a:1b
inet 192.168.42.17 netmask 0xff00 broadcast 192.168.42.255
inet 192.168.42.18 netmask 0x broadcast 192.168.42.18
inet 192.168.42.19 netmask 0x broadcast 192.168.42.19
inet 192.168.42.20 netmask 0x broadcast 192.168.42.20
inet 192.168.42.21 netmask 0x broadcast 192.168.42.21
inet 192.168.42.23 netmask 0x broadcast 192.168.42.23
inet 192.168.42.24 netmask 0x broadcast 192.168.42.24
media: Ethernet autoselect (1000baseT )
status: active

Are you using NAT from your jail to the outside world?

Patrick


On Tue, Aug 27, 2013 at 2:21 PM, Alejandro Imass  wrote:
> On Tue, Aug 27, 2013 at 4:59 PM, Alejandro Imass  wrote:
>> Hi,
>>
>> I have a machine with several public IPs on the same NIC and I bound
>> one of those IPs to a jail created with EzJail. Suppose the scenario
>> is something like this:
>>
>> em0
>> 190.100.100.1
>> 190.100.100.2
>> 190.100.100.3
>> 190.100.100.4
>>
>> In the jail we are bound only to 190.100.100.4
>>
>> The default router is correctly set on the jail, etc.
>>
>> But when we ssh out of that jail, or send an email, the receiving end
>> always sees 190.100.100.1 not 190.100.100.4 which is the IP the jail
>> is bound to.
>
>
> I think my problem is actually more basic than this. The problem
> actually occurs on the base system as well and I think it's because
> all the IPs are on the same subnet, then the kernel assumes to use the
> primary IP as the source address. For the sake and usefulness of the
> mail archives I will end this thread here and start another one with a
> more appropriate title, not before researching to see if this can be
> done with the routing table or if I need to use ipfw to re-write the
> source address.
>
> Thanks,
>
> --
> Alejandro Imass
> ___
> 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"
___
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: Jail with public IP alias

2013-08-27 Thread Alejandro Imass 
On Tue, Aug 27, 2013 at 6:28 PM, Patrick  wrote:
> That's not the behaviour I see. My jail has a private and public IP.
>

Hi Patrick, thanks for your reply.

The issue is actually more basic and it's because the same network
card has multiple IPs on the same subnet so the routing table always
chooses the primary IP assigned to that interface.

I'm trying to figure out if I can fix it in the routing table or will
need IPFW to re-write the source address.

Thanks,

-- 
Alejandro Imass
___
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: Way to be announced about security updates and new releases

2013-08-27 Thread Olivier Nicole 
FreeBSD announce mailing list...

Sexurity announcement (at least) are also cross posted on FreeBSD questions.

Olivier

On Tue, Aug 27, 2013 at 9:34 PM, Zyumbilev, Peter
 wrote:
> http://www.freebsd.org/security/rss.xml
>
> ?
> Peter
>
> On 21/08/2013 09:54, Antonio Kless wrote:
>> Is there any way to be noticed, when security updates or new releases are
>> available?
>>
>> https://twitter.com/freebsd nearly would be a solution, if it did not
>> repostquestions from its
>> subscribers and other information that is not related to updates.
>>
> ___
> 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"
___
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: Jail with public IP alias

2013-08-27 Thread Patrick 
Hi Alejandro,

That's how I've got things setup, too, but I'm not seeing the same
behaviour. So I was wondering if there was something different about
your setup such as using NAT to allow a jail with a private IP to
access the internet at large.

Patrick


On Tue, Aug 27, 2013 at 3:42 PM, Alejandro Imass  wrote:
> On Tue, Aug 27, 2013 at 6:28 PM, Patrick  wrote:
>> That's not the behaviour I see. My jail has a private and public IP.
>>
>
> Hi Patrick, thanks for your reply.
>
> The issue is actually more basic and it's because the same network
> card has multiple IPs on the same subnet so the routing table always
> chooses the primary IP assigned to that interface.
>
> I'm trying to figure out if I can fix it in the routing table or will
> need IPFW to re-write the source address.
>
> Thanks,
>
> --
> Alejandro Imass
___
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"

distfiles changed to new path

2013-08-27 Thread Fbsd8 

I just did a portsnap run that updated the base port system.

Now I see a port's distfile going to /var/ports/distfiles instead of
/usr/ports/distfiles.

Is this a error in the newly updated base port system which contains the 
default port make environment?


___
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: Renumber users and groups

2013-08-27 Thread Olivier Nicole 
One last comment, for the records,

>>> Those solutions sound pretty handy if I need to move the files at the
>>> same time. mtree should do this in-place with minimal fuss as it's just
>>> confirming permissions and ownership on all files.
>> I also just thought of an idea I need to benchmark: running mtree with
>> and without nscd. I bet nscd could speed it up a lot.
>
> I did try mtree on my own files, counting for 20% of the total size,
> and it took only seconds.
>
> I bet other users may have many more smaller files, but it's all a
> matter of minutes, so it is fast enough.

I found out that mtree would not renumber the symbolic links, so i had
to solve that urgently afterward.

Best regards,

Olivier
___
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"