unbound error: Undefined symbol "sldns_key_EVP_load_gost_id"
Hi, Haven't seen this reported yet, so here it is. Found on last week's world, rebuild last night and still there. Worth filing a bug? storm~;uname -a FreeBSD storm 13.0-CURRENT FreeBSD 13.0-CURRENT r339863 GENERIC amd64 Trying to run unbound, and: storm~;sudo unbound -dd ld-elf.so.1: /usr/sbin/unbound: Undefined symbol "sldns_key_EVP_load_gost_id" The voices in my head mutter it's something about OpenSSL. But they're usually wrong. Here's my unbound.conf, just in case: --- root-hints: "named.cache" access-control: 0.0.0.0/0 allow --- Thanks, ==ml -- Michael W. Lucashttps://mwl.io/ author of: Absolute OpenBSD, SSH Mastery, git commit murder, Immortal Clay, PGP & GPG, Absolute FreeBSD, etc, etc, etc... ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: jail exec.clean busted in 12?
On Tue, Sep 11, 2018 at 06:55:56PM -0400, Shawn Webb wrote:
> On Tue, Sep 11, 2018 at 03:58:02PM -0400, Michael W. Lucas wrote:
> >
> > Hi,
> >
> > storm~;uname -a
> > FreeBSD storm 12.0-ALPHA4 FreeBSD 12.0-ALPHA4 #10 r338496: Thu Sep 6
> > 12:29:00 EDT 2018 root@storm:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
> > amd64
> >
> > It appears that exec.clean is busted. Here's my jail.conf:
> >
> > ---
> >
> > $j="/jail";
> > path="$j/$name";
> > host.hostname="$name.mwl.io";
> >
> > mount.devfs;
> > exec.clean=0;
> > exec.start="sh /etc/rc";
> > exec.stop="sh /etc/rc.shutdown";
> >
> > loghost {
> > ip4.addr="203.0.113.231";
> > allow.raw_sockets=1;
> > jid=99;
> > }
> >
> > logdb {
> > host.hostname="logdb.mwl.io";
> > ip4.addr="203.0.113.232";
> > }
> >
> > ---
> >
> > exec.clean is not explicitly defined on the command line, but it's the
> > default, so it maybe shouldn't be?
> >
> > storm~;jls -n
> > devfs_ruleset=0 nodying enforce_statfs=2 host=new ip4=disable ip6=disable
> > jid=8 linux=new name=logdb osreldate=1200084 osrelease=12.0-ALPHA4 parent=0
> > path=/jail/logdb nopersist securelevel=-1 sysvmsg=disable sysvsem=disable
> > sysvshm=disable vnet=inherit allow.nochflags allow.nomlock allow.nomount
> > allow.mount.nodevfs allow.mount.nofdescfs allow.mount.nolinprocfs
> > allow.mount.nonullfs allow.mount.noprocfs allow.mount.notmpfs
> > allow.mount.nozfs allow.noquotas allow.noraw_sockets allow.reserved_ports
> > allow.set_hostname allow.nosocket_af allow.nosysvipc children.cur=0
> > children.max=0 cpuset.id=6 host.domainname="" host.hostid=0
> > host.hostname=logdb.mwl.io
> > host.hostuuid=---- ip4.addr=203.0.113.232
> > ip4.saddrsel ip6.addr= ip6.saddrsel linux.osname=Linux
> > linux.osrelease=2.6.32 linux.oss_version=198144
> > devfs_ruleset=0 nodying enforce_statfs=2 host=new ip4=disable ip6=disable
> > jid=99 linux=new name=loghost osreldate=1200084 osrelease=12.0-ALPHA4
> > parent=0 path=/jail/loghost nopersist securelevel=-1 sysvmsg=disable
> > sysvsem=disable sysvshm=disable vnet=inherit allow.nochflags allow.nomlock
> > allow.nomount allow.mount.nodevfs allow.mount.nofdescfs
> > allow.mount.nolinprocfs allow.mount.nonullfs allow.mount.noprocfs
> > allow.mount.notmpfs allow.mount.nozfs allow.noquotas allow.raw_sockets
> > allow.reserved_ports allow.set_hostname allow.nosocket_af allow.nosysvipc
> > children.cur=0 children.max=0 cpuset.id=7 host.domainname="" host.hostid=0
> > host.hostname=loghost.mwl.io
> > host.hostuuid=---- ip4.addr=203.0.113.231
> > ip4.saddrsel ip6.addr= ip6.saddrsel linux.osname=Linux
> > linux.osrelease=2.6.32 linux.oss_version=198144
> >
> > Anyway, I found this by:
> >
> > # jexec loghost env
> > HOME=/home/mwlucas
> > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/home/mwlucas/bin
> > TERM=xterm
> > LC_COLLATE=C
> > LANG=en_US.UTF-8
> > SSH_CLIENT=203.0.113.70 59076 22
> > SSH_CONNECTION=203.0.113.70 59076 203.0.113.50 22
> > SSH_TTY=/dev/pts/2
> > SSH_AUTH_SOCK=/tmp/ssh-ZfvZOatcsu/agent.60492
> > LC_CTYPE=en_US.ISO-8859-1
> > MAIL=/var/mail/root
> > ...
> >
> > I'm highly confident my SSH environment shouldn't be in the jail. Yes,
> > it goes away if I add -l, but my (admittedly sketchy) reading of the
> > jexec source says that jexec handles stripping the environment before
> > running the command.
> >
> > Even if I start it the hard way (from a discussion at
> > https://github.com/iocage/iocage/issues/610)
> >
> > storm~;jail -c path=/jail/loghost/ host.hostname=loghost exec.clean=1
> > persist
> > storm~;jls
> >JID IP Address Hostname Path
> > 9 loghost /jail/loghost
> >
> > storm~;jexec 9 env | grep -i ssh
> > SSH_CLIENT=203.0.113.70 59076 22
> > SSH_CONNECTION=203.0.113.70 59076 203.0.113.50 22
> > SSH_TTY=/dev/pts/2
> > SSH_AUTH_SOCK=/tmp/ssh-ZfvZOatcsu/agent.60492
> > storm~;
> >
> > Any ideas?
>
> Hey Michael,
>
> It appears the jail.exec option is for jail(8) only.
Ah, okay. Thanks. Not obvious, but makes sense.
(So you can run your dirty environment in the jail through jexec? Cool.)
==ml
> You need to pass
> the -l option to jexec(8) to sanitize the environment.
>
> Thanks,
>
> --
> Shawn Webb
> Cofounder and Security Engineer
> HardenedBSD
>
> Tor-ified Signal:+1 443-546-8752
> Tor+XMPP+OTR:latt...@is.a.hacker.sx
> GPG Key ID: 0x6A84658F52456EEE
> GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE
--
Michael W. Lucashttps://mwl.io/
author of: Absolute OpenBSD, SSH Mastery, git commit murder,
Immortal Clay, PGP & GPG, Absolute FreeBSD, etc, etc, etc...
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
jail exec.clean busted in 12?
Hi,
storm~;uname -a
FreeBSD storm 12.0-ALPHA4 FreeBSD 12.0-ALPHA4 #10 r338496: Thu Sep 6 12:29:00
EDT 2018 root@storm:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
It appears that exec.clean is busted. Here's my jail.conf:
---
$j="/jail";
path="$j/$name";
host.hostname="$name.mwl.io";
mount.devfs;
exec.clean=0;
exec.start="sh /etc/rc";
exec.stop="sh /etc/rc.shutdown";
loghost {
ip4.addr="203.0.113.231";
allow.raw_sockets=1;
jid=99;
}
logdb {
host.hostname="logdb.mwl.io";
ip4.addr="203.0.113.232";
}
---
exec.clean is not explicitly defined on the command line, but it's the
default, so it maybe shouldn't be?
storm~;jls -n
devfs_ruleset=0 nodying enforce_statfs=2 host=new ip4=disable ip6=disable jid=8
linux=new name=logdb osreldate=1200084 osrelease=12.0-ALPHA4 parent=0
path=/jail/logdb nopersist securelevel=-1 sysvmsg=disable sysvsem=disable
sysvshm=disable vnet=inherit allow.nochflags allow.nomlock allow.nomount
allow.mount.nodevfs allow.mount.nofdescfs allow.mount.nolinprocfs
allow.mount.nonullfs allow.mount.noprocfs allow.mount.notmpfs allow.mount.nozfs
allow.noquotas allow.noraw_sockets allow.reserved_ports allow.set_hostname
allow.nosocket_af allow.nosysvipc children.cur=0 children.max=0 cpuset.id=6
host.domainname="" host.hostid=0 host.hostname=logdb.mwl.io
host.hostuuid=---- ip4.addr=203.0.113.232
ip4.saddrsel ip6.addr= ip6.saddrsel linux.osname=Linux linux.osrelease=2.6.32
linux.oss_version=198144
devfs_ruleset=0 nodying enforce_statfs=2 host=new ip4=disable ip6=disable
jid=99 linux=new name=loghost osreldate=1200084 osrelease=12.0-ALPHA4 parent=0
path=/jail/loghost nopersist securelevel=-1 sysvmsg=disable sysvsem=disable
sysvshm=disable vnet=inherit allow.nochflags allow.nomlock allow.nomount
allow.mount.nodevfs allow.mount.nofdescfs allow.mount.nolinprocfs
allow.mount.nonullfs allow.mount.noprocfs allow.mount.notmpfs allow.mount.nozfs
allow.noquotas allow.raw_sockets allow.reserved_ports allow.set_hostname
allow.nosocket_af allow.nosysvipc children.cur=0 children.max=0 cpuset.id=7
host.domainname="" host.hostid=0 host.hostname=loghost.mwl.io
host.hostuuid=---- ip4.addr=203.0.113.231
ip4.saddrsel ip6.addr= ip6.saddrsel linux.osname=Linux linux.osrelease=2.6.32
linux.oss_version=198144
Anyway, I found this by:
# jexec loghost env
HOME=/home/mwlucas
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/home/mwlucas/bin
TERM=xterm
LC_COLLATE=C
LANG=en_US.UTF-8
SSH_CLIENT=203.0.113.70 59076 22
SSH_CONNECTION=203.0.113.70 59076 203.0.113.50 22
SSH_TTY=/dev/pts/2
SSH_AUTH_SOCK=/tmp/ssh-ZfvZOatcsu/agent.60492
LC_CTYPE=en_US.ISO-8859-1
MAIL=/var/mail/root
...
I'm highly confident my SSH environment shouldn't be in the jail. Yes,
it goes away if I add -l, but my (admittedly sketchy) reading of the
jexec source says that jexec handles stripping the environment before
running the command.
Even if I start it the hard way (from a discussion at
https://github.com/iocage/iocage/issues/610)
storm~;jail -c path=/jail/loghost/ host.hostname=loghost exec.clean=1 persist
storm~;jls
JID IP Address Hostname Path
9 loghost /jail/loghost
storm~;jexec 9 env | grep -i ssh
SSH_CLIENT=203.0.113.70 59076 22
SSH_CONNECTION=203.0.113.70 59076 203.0.113.50 22
SSH_TTY=/dev/pts/2
SSH_AUTH_SOCK=/tmp/ssh-ZfvZOatcsu/agent.60492
storm~;
Any ideas?
Thanks,
==ml
--
Michael W. Lucashttps://mwl.io/
author of: Absolute OpenBSD, SSH Mastery, git commit murder,
Immortal Clay, PGP & GPG, Absolute FreeBSD, etc, etc, etc...
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
should MINIMAL boot?
Hi, Tried booting MINIMAL on last weekend's current, on both UFS and ZFS hosts in VirtualBox. Neither could find its boot drive. Before I dive deeper and file a bug, wanted to ask: Should a MINIMAL kernel boot and run? If not, I won't waste my time. Thanks, ==ml -- Michael W. Lucashttps://mwl.io/ nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: old snapshot install images?
On Wed, May 03, 2017 at 09:11:05PM +0300, Toomas Soome wrote: > > > On 3. mai 2017, at 21:06, Michael W. Lucas > > wrote: > > > > On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote: > >> There was many issues fixed step by step and some fixes for particular > >> problem did reveal next one (at least in some systems), and indeed, it can > >> cause some problems if you are caught in middle of updates. From my point > >> of view, the most important question is if the current ???current??? is > >> ok:) > > > > > > Agreed 500%. > > > > The latest snapshot is NOT ok. > > > > What is the error there? error 1 error 1 gptzfsboot: error 1 lba 4294967288 gptzfsboot: error 1 lba 1 gptzfsboot: no ZFS pools located, can't boot My first thought was that the BIOS was looking at a different drive, not the SATADOMs, so I disabled booting from all the spinning drives in the BIOS. On a related note: my script at http://www-old.michaelwlucas.com/zm.sh also gives the same error at boot. -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: old snapshot install images?
On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote: > There was many issues fixed step by step and some fixes for particular > problem did reveal next one (at least in some systems), and indeed, it can > cause some problems if you are caught in middle of updates. From my point of > view, the most important question is if the current ???current??? is ok:) Agreed 500%. The latest snapshot is NOT ok. ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: old snapshot install images?
On Wed, May 03, 2017 at 09:52:09AM -0700, Ngie Cooper wrote: > Ok. How big is your freebsd-boot partition? The size created by the installer. ;) I've run another install, this one with the r317181 snapshot (20 April.) gpart show ada4 shows this (hand-copied) 40 125045344ada4 GPT (60G) 40 1024 1 freebsd-boot (512K) 1064 984- free - (492K) 2048 4194304 2 freebsd-swap (2.0G) 41963521208483843 freebsd-zfs (58G) 125044736 648- free - (324K) ada5 is identical. It's a two-satadom mirror. I used the guided install, had it blow the disks away. ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: old snapshot install images?
On Wed, May 03, 2017 at 09:37:04AM -0700, Ngie Cooper (yaneurabeya) wrote: > Ok. I was curious because there has been a period of time when 512b/sector > disks have been broken and vice versa. > > I???m going to operate under the impression that one of tsoome???s recent > changes to zfsboot fixed things (there was some breakage over the past couple > months based on posts to current@ and svn-src-*@), but I can???t count on it > 100%. The most recent installer snapshot has the exact same problem. Every installer snapshot on the FTP site has the exact same problem. I've gotten some installer snapshots from October and from mid-2015. Trying those. My goal is to find out when the problem appeared and include the time window in the PR. ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: old snapshot install images?
On Wed, May 03, 2017 at 01:01:10AM -0700, Ngie Cooper wrote: > Hi Michael! > - What sources are you using/revision are you at? Using r311461 amd64 install memstick at the moment. Uname says built "Thu Jan 5 22:46:38 UTC 2017" > - Are your drives the 512 byte/sector or 4kB/sector variety? They all claim to be 512 byte/sector. FWIW. ;-) ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
old snapshot install images?
Hi, About a year ago, I did a clean install on my desktop. No problems. I tried a clean install now, and it dies with: gtpzfsboot: error 1 lba 32 error 1 gptzfsboot: error 1 lba 4294967288 gptzfsboot: error 1 lba 1 gptzfsboot: no ZFS pools located, can't boot The pool is visible in the live CD, and I can import it. I want to file a PR. The sensible thing for me to do is to use old snapshot installers to determine when this machine could no longer install. Unfortunately, the FTP servers only keep a month or so of snapshots. ftp-archive doesn't have the old snapshots. Does anyone have an archive of -current install media, either CD or ISO? I need to get this box back fairly quickly, but I don't mind burning a couple days to nail it down. Thanks, ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: two recent snapshot installer problems
Thanks for the hint, Toomas. But... I updated my custom ZFS install/partition script, at: http://www-old.michaelwlucas.com/zm.sh I used this script at the command line partitioner in the installer, then exited and let the installer take over. The machine installs. After a "sysrc zfs_enable=yes" it boots. So: bsdinstall doesn't like this box. If anyone's willing to work on the installer in the next few days, I'm willing to wait to work on this box. I will have to put it to work before long, though. Thanks, ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
two recent snapshot installer problems
Hi, I want to open a bug report on this, but have no idea how to gather useful info. Attempting to install FreeBSD-12.0-CURRENT-amd64-20170301-r314495-memstick.img onto an eight-drive iX system. This machine previously ran -current, but the OS has been sadly used by book testing and I decided to do a clean install. Used the Guided ZFS install, no networking, no extra users, default security. I want a two-way mirror for the base install, and the BIOS didn't provide serial numbers for each disk, so I wound up doing multiple installs, thinking that once I installed to the disk that the BIOS expected to be a boot disk, it'd find the pool and boot. Each of the four installs failed to boot, giving me: gptzfsboot: error 1 lba 32 error 1 gptzfsboot: error 1 lba 4294967288 gptzfsboot: error 1 lba 1 gptzfsboot: No ZFS pools located, can't boot Old disklabels? gpart -F destroy da0 through ada3. and reinstall. Nope. In frustration I did an eight-disk mirror install. Got the same message. Fine, I'll install to the Intel RAID satadom. It's a raid config, but it'll get me a working system. Select a ZFS stripe on raid/r0. gpart: arg0 'raid/r0': Invalid argument Mirror on the individual satadom drives? Same boot message. Any suggestions on how to gather debugging info for this? Thanks, ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/ blog: http://blather.michaelwlucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
zfs/unionfs panic on last night's -current
Hi, I'm experimenting with unionfs for my next FreeBSD book, and found a reproducible panic. I haven't needed to report a panic for... uh... I don't think I've done it this century, so I might be a wee bit wrong in what you need... please correct me if you need other info. I have a ZFS pool called jails, with two datasets: jails/basejail and jails/jail1. I want jail1 mounted over basejail, at the jail1 mount point. # cd jails # mount_unionfs -o below basejail/ jail1/ And I get: panic: solaris assert: cnp->cn_namelen < sizeof(nm), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 6213 Info: Dump header from device: /dev/gpt/swap0 Architecture: amd64 Architecture Version: 2 Dump Length: 2351693824 Blocksize: 512 Dumptime: Wed Sep 2 10:23:58 2015 Hostname: storm Magic: FreeBSD Kernel Dump Version String: FreeBSD 11.0-CURRENT #0 r287374: Tue Sep 1 15:31:17 EDT 2015 root@storm:/usr/obj/usr/src/sys/GENERIC Panic String: solaris assert: cnp->cn_namelen < sizeof(nm), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 6213 Dump Parity: 1813619135 Bounds: 3 Dump Status: good Full panic info at: http://www-old.michaelwlucas.com/core.txt.3 but here's the top of the message. Unread portion of the kernel message buffer: panic: solaris assert: cnp->cn_namelen < sizeof(nm), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: 6213 cpuid = 3 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe085d0cc360 vpanic() at vpanic+0x189/frame 0xfe085d0cc3e0 panic() at panic+0x43/frame 0xfe085d0cc440 assfail() at assfail+0x1a/frame 0xfe085d0cc450 zfs_freebsd_lookup() at zfs_freebsd_lookup+0x47/frame 0xfe085d0cc590 VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0xf1/frame 0xfe085d0cc5c0 vfs_cache_lookup() at vfs_cache_lookup+0xd6/frame 0xfe085d0cc620 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xf1/frame 0xfe085d0cc650 relookup() at relookup+0xa1/frame 0xfe085d0cc6b0 unionfs_relookup() at unionfs_relookup+0x105/frame 0xfe085d0cc710 unionfs_relookup_for_delete() at unionfs_relookup_for_delete+0x56/frame 0xfe085d0cc7a0 unionfs_rmdir() at unionfs_rmdir+0xd1/frame 0xfe085d0cc800 VOP_RMDIR_APV() at VOP_RMDIR_APV+0xf7/frame 0xfe085d0cc830 kern_rmdirat() at kern_rmdirat+0x1bc/frame 0xfe085d0cc9a0 amd64_syscall() at amd64_syscall+0x282/frame 0xfe085d0ccab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe085d0ccab0 --- syscall (137, FreeBSD ELF64, sys_rmdir), rip = 0x80089341a, rsp = 0x7fffe8f8, rbp = 0x7fffe930 --- KDB: enter: panic Thanks! ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: zfs/unionfs panic on last night's -current
I forgot the command that triggers the panic! My apologies. # cd /jails/jail1 # rmdir proc panic! The jail is not running, no procfs is mounted. On Wed, Sep 02, 2015 at 10:41:57AM -0400, Michael W. Lucas wrote: > Hi, > > I'm experimenting with unionfs for my next FreeBSD book, and found a > reproducible panic. I haven't needed to report a panic for... uh... I > don't think I've done it this century, so I might be a wee bit wrong > in what you need... please correct me if you need other info. > > I have a ZFS pool called jails, with two datasets: jails/basejail and > jails/jail1. I want jail1 mounted over basejail, at the jail1 mount > point. > > # cd jails > # mount_unionfs -o below basejail/ jail1/ > > And I get: > > panic: solaris assert: cnp->cn_namelen < sizeof(nm), file: > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: > 6213 > > Info: > > Dump header from device: /dev/gpt/swap0 > Architecture: amd64 > Architecture Version: 2 > Dump Length: 2351693824 > Blocksize: 512 > Dumptime: Wed Sep 2 10:23:58 2015 > Hostname: storm > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 11.0-CURRENT #0 r287374: Tue Sep 1 15:31:17 EDT 2015 > root@storm:/usr/obj/usr/src/sys/GENERIC > Panic String: solaris assert: cnp->cn_namelen < sizeof(nm), file: > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: > 6213 > Dump Parity: 1813619135 > Bounds: 3 > Dump Status: good > > Full panic info at: http://www-old.michaelwlucas.com/core.txt.3 > but here's the top of the message. > > Unread portion of the kernel message buffer: > panic: solaris assert: cnp->cn_namelen < sizeof(nm), file: > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c, line: > 6213 > cpuid = 3 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe085d0cc360 > vpanic() at vpanic+0x189/frame 0xfe085d0cc3e0 > panic() at panic+0x43/frame 0xfe085d0cc440 > assfail() at assfail+0x1a/frame 0xfe085d0cc450 > zfs_freebsd_lookup() at zfs_freebsd_lookup+0x47/frame 0xfe085d0cc590 > VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0xf1/frame 0xfe085d0cc5c0 > vfs_cache_lookup() at vfs_cache_lookup+0xd6/frame 0xfe085d0cc620 > VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xf1/frame 0xfe085d0cc650 > relookup() at relookup+0xa1/frame 0xfe085d0cc6b0 > unionfs_relookup() at unionfs_relookup+0x105/frame 0xfe085d0cc710 > unionfs_relookup_for_delete() at unionfs_relookup_for_delete+0x56/frame > 0xfe085d0cc7a0 > unionfs_rmdir() at unionfs_rmdir+0xd1/frame 0xfe085d0cc800 > VOP_RMDIR_APV() at VOP_RMDIR_APV+0xf7/frame 0xfe085d0cc830 > kern_rmdirat() at kern_rmdirat+0x1bc/frame 0xfe085d0cc9a0 > amd64_syscall() at amd64_syscall+0x282/frame 0xfe085d0ccab0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe085d0ccab0 > --- syscall (137, FreeBSD ELF64, sys_rmdir), rip = 0x80089341a, rsp = > 0x7fffe8f8, rbp = 0x7fffe930 --- > KDB: enter: panic > > Thanks! > ==ml > > -- > Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor > http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
gbde destroy doesn't match man page?
Hi, Playing with GBDE for my FreeBSD disk book, on: # uname -a FreeBSD storm 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r269010: Wed Jul 23 11:13:17 EDT 2014 mwlucas@storm:/usr/obj/usr/src/sys/GENERIC amd64 According to the man page, I should be able to destroy all copies of the key with gbde destroy -n -1. It's in the examples. When I try it I get: # gbde destroy da0p1 -n -1 gbde: illegal option -- n usage: gbde attach destination [-k keyfile] [-l lockfile] [-p pass-phrase] gbde detach destination gbde init destination [-i] [-f filename] [-K new-keyfile] [-L new-lockfile] [-P new-pass-phrase] gbde setkey destination [-n key] [-k keyfile] [-l lockfile] [-p pass-phrase] [-K new-keyfile] [-L new-lockfile] [-P new-pass-phrase] gbde nuke destination [-n key] [-k keyfile] [-l lockfile] [-p pass-phrase] gbde destroy destination [-k keyfile] [-l lockfile] [-p pass-phrase] Anyone know if this is a software bug or a doc bug? Thanks, ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: libressl anyone?
On Fri, Jul 11, 2014 at 04:12:42PM -0700, Kevin Oberman wrote: > Now that OpenBSD has released LibreSSL, can someone port it? And maybe try > putting it into head? I'd love to see OpenSSL gone yesterday. > > The initial portable LibreSSL is available from > http://ftp.openbsd.org/pub/OpenBSD/LibreSSL. Note that the OpenBSD folks > say that this release is intended for testing and evealuation, so it is not > a candidate for any stable or release, but it does build on FreeBSD. > > Yes, if I get some time today or tomorrow, I'll try to write up a port, but > I'm still far from comfortable with the new porting stuff, so it will > likely take longer that I'd like. Others can probably knock it out in > nothing flat. Check out the discussion on t...@openbsd.org. A fair amount of software is breaking with LibreSSL. For example, LibreSSL dropped EGD support. Various software (eg Python) checks for egd, and won't build without EGD. Mind you, people should certainly try it and see what happens. ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: diskid documentation
On Mon, Jun 02, 2014 at 10:45:52AM -0400, Ryan Stone wrote: > On Mon, Jun 2, 2014 at 9:26 AM, Allan Jude wrote: > > It also tends to sometimes hide the gpt label provider on me (not sure > > in which cases it does this, but it is annoying) > > This happens when something (e.g. zfs) happens to open the diskid > provider instead of the gpt label. For me this ended up being a bit > more than annoying; my swap was mounted in /etc/fstab via a gpt label > so I silently lost my swap when I did an upgrade. Wait-- one type of one label can hide another? I thought a big point of labels was to remove ambiguity... ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
diskid documentation
Hi, I'm trying to track down the documentation for the /dev/diskid/blah device nodes. Is there a man page? It appears that this is a current-only thing, so I'm asking here? (At least, none of my 9.x or 10.x machines have /dev/diskid.) Thanks, ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
problem building -current
Hi, I'm running an older -current: bewilderbeast/usr/src;uname -a FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT #15: Thu Nov 8 14:02:45 EST 2012 mwlu...@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/G Trying to build new, and get: ... c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"\" -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/PluginLoader.cpp -o PluginLoader.o c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"\" -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/PrettyStackTrace.cpp -o PrettyStackTrace.o c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"\" -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp -o Process.o In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp:85: /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc: In member function 'virtual llvm::sys::TimeValue llvm::sys::self_process::get_user_time() const': /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:75: error: 'CLOCK_PROCESS_CPUTIME_ID' was not declared in this scope *** [Process.o] Error code 1 Stop in /usr/src/lib/clang/libllvmsupport. *** [bootstrap-tools] Error code 1 Stop in /usr/src. *** [_bootstrap-tools] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. /etc/src.conf: SENDMAIL_MC=/etc/mail/bwb.mc WITHOUT_BIND=YES SENDMAIL_MC=/etc/mail/bwb.mc PERL_VERSION=5.10.1 WITHOUT_PKGNG=yes # added by use.perl 2012-11-15 11:47:34 PERL_VERSION=5.14.2 I don't see any references to this error anywhere in the FreeBSD lists. Any ideas how to get past it? Or should I just upgrade from snapshot and try again? Thanks, ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code "ILUVMICHAEL" gets you 30% off & helps me. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: after upgrade, can't restart apache via cron
On Thu, Nov 22, 2012 at 09:33:34PM -0600, Adam Vande More wrote: >I would guess you need*/usr/sbin/ in cron's path. Thanks everyone. The real problem here was, I didn't know setfib was a command... ==ml -- Michael W. Lucas http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Latest book: SSH Mastery http://www.michaelwlucas.com/nonfiction/ssh-mastery mwlu...@michaelwlucas.com, Twitter @mwlauthor ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
after upgrade, can't restart apache via cron
FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT #15: Thu Nov 8 14:02:45 EST 2012 mwlu...@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC amd64 I can manually restart apache22 with the following /etc/rc.conf entries: apache22_enable="YES" apache22_fib=0 I have a cron entry that restarts apache regularly, to compensate for some mysql daftness. 13 * * * * /usr/local/etc/rc.d/apache22 restart When this job runs, I get the following email: Performing sanity check on apache22 configuration: Syntax OK Stopping apache22. Waiting for PIDS: 59501. Performing sanity check on apache22 configuration: Syntax OK Starting apache22. eval: setfib: not found /usr/local/etc/rc.d/apache22: WARNING: failed to start apache22 If I run /usr/local/etc/rc.d/apache22 restart from the command line, I can restart httpd without trouble. Any thoughts? ==ml -- Michael W. Lucas http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Latest book: SSH Mastery http://www.michaelwlucas.com/nonfiction/ssh-mastery mwlu...@michaelwlucas.com, Twitter @mwlauthor ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 9.0/i386 build failure
On Sat, Nov 05, 2011 at 09:41:36PM +0200, Kostik Belousov wrote: > Personally, I would install from any snapshot, 9.0RC1 is good enough for > later HEAD rebuild. Thank you, gentlemen! I believe that upgrading via snapshot is the smart solution here. But it'll be in the archives for anyone else bit by this issue. ==ml -- Michael W. Lucas http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Latest book: Network Flow Analysis http://www.networkflowanalysis.com/ mwlu...@blackhelicopters.org, Twitter @mwlauthor ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
9.0/i386 build failure
I suspect I'm building on a system that's too old, but it's worth asking. FreeBSD eyeball.lodden.com 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Sat Aug 29 00:31:14 EDT 2009 mwlu...@stretchlimo.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC i386 csup today. no /etc/src.conf, /etc/make.conf only contains a perl definition. ... c++ -O2 -pipe -I/usr/src/usr.bin/clang/tblgen/../../../contrib/llvm/include -I/usr/src/usr.bin/clang/tblgen/../../../contrib/llvm/tools/clang/include -I/usr/src/usr.bin/clang/tblgen/../../../contrib/llvm/utils/TableGen -I. -I/usr/src/usr.bin/clang/tblgen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"i386-unknown-freebsd9.0\" -I/usr/obj/usr/src/tmp/legacy/usr/include -static -L/usr/obj/usr/src/tmp/legacy/usr/lib -o tblgen ARMDecoderEmitter.o AsmMatcherEmitter.o AsmWriterEmitter.o AsmWriterInst.o CallingConvEmitter.o CodeEmitterGen.o CodeGenDAGPatterns.o CodeGenInstruction.o CodeGenRegisters.o CodeGenTarget.o DAGISelEmitter.o DAGISelMatcher.o DAGISelMatcherEmitter.o DAGISelMatcherGen.o DAGISelMatcherOpt.o DisassemblerEmitter.o EDEmitter.o FastISelEmitter.o FixedLenDecoderEmitter.o InstrEnumEmitter.o InstrInfoEmitter.o IntrinsicEmitter.o PseudoLoweringEmitter.o RegisterInfoEmitter.o SetTheory.o StringMatcher.o SubtargetEmitter.o TGValueTypes.o TableGen.o X86DisassemblerTables.o X86RecognizableInstr.o /usr/obj/usr/src/tmp/usr/src/usr.bin/clang/tblgen/../../../lib/clang/libllvmtablegen/libllvmtablegen.a /usr/obj/usr/src/tmp/usr/src/usr.bin/clang/tblgen/../../../lib/clang/libllvmsupport/libllvmsupport.a -legacy /usr/obj/usr/src/tmp/usr/src/usr.bin/clang/tblgen/../../../lib/clang/libllvmsupport/libllvmsupport.a(Atomic.o)(.text+0x25): In function `llvm::sys::AtomicIncrement(unsigned int volatile*)': : undefined reference to `__sync_add_and_fetch_4' /usr/obj/usr/src/tmp/usr/src/usr.bin/clang/tblgen/../../../lib/clang/libllvmsupport/libllvmsupport.a(Atomic.o)(.text+0x45): In function `llvm::sys::AtomicDecrement(unsigned int volatile*)': : undefined reference to `__sync_sub_and_fetch_4' /usr/obj/usr/src/tmp/usr/src/usr.bin/clang/tblgen/../../../lib/clang/libllvmsupport/libllvmsupport.a(Atomic.o)(.text+0x5): In function `llvm::sys::AtomicAdd(unsigned int volatile*, unsigned int)': : undefined reference to `__sync_add_and_fetch_4' /usr/obj/usr/src/tmp/usr/src/usr.bin/clang/tblgen/../../../lib/clang/libllvmsupport/libllvmsupport.a(Atomic.o)(.text+0x61): In function `llvm::sys::CompareAndSwap(unsigned int volatile*, unsigned int, unsigned int)': : undefined reference to `__sync_val_compare_and_swap_4' *** Error code 1 Stop in /usr/src/usr.bin/clang/tblgen. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 -- Michael W. Lucas http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Latest book: Network Flow Analysis http://www.networkflowanalysis.com/ mwlu...@blackhelicopters.org, Twitter @mwlauthor ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Apache 2.2 port and missing modules on current.
Hi, This bit me as well. Some experimentation showed that a few apache functions are now compiled in, rather than being modules. Don't know why. Editing httpd.conf to remove the items that were no longer modules restored service. ==ml On Tue, Aug 10, 2010 at 05:52:43PM +0200, Bartosz Stec wrote: > On 2010-08-10 17:23, Ilya A. Arhipov wrote: > >make config and add > >[x] THREADS Enable threads support in APR :) > >and deinstall&& reinstall > > > >10.08.10, 18:07, "Bartosz Stec": > > > Arrgh! My mistake - I showed generic > /usr/ports/www/apache22/Makefile.options instead of > /var/db/ports/apache22/options. So here's the correct one: > ># This file is auto-generated by 'make config'. ># No user-servicable parts inside! ># Options for apache-2.2.16 >_OPTIONS_READ=apache-2.2.16 >WITH_THREADS=true >WITHOUT_MYSQL=true >WITHOUT_PGSQL=true >WITHOUT_SQLITE=true >WITH_IPV6=true >WITHOUT_BDB=true >WITH_AUTH_BASIC=true >WITH_AUTH_DIGEST=true >WITH_AUTHN_FILE=true >WITHOUT_AUTHN_DBD=true >WITH_AUTHN_DBM=true >WITH_AUTHN_ANON=true >WITH_AUTHN_DEFAULT=true >WITH_AUTHN_ALIAS=true >WITH_AUTHZ_HOST=true >WITH_AUTHZ_GROUPFILE=true >WITH_AUTHZ_USER=true >WITH_AUTHZ_DBM=true >WITH_AUTHZ_OWNER=true >WITH_AUTHZ_DEFAULT=true >WITH_CACHE=true >WITH_DISK_CACHE=true >WITH_FILE_CACHE=true >WITHOUT_MEM_CACHE=true >WITH_DAV=true >WITH_DAV_FS=true >WITHOUT_BUCKETEER=true >WITHOUT_CASE_FILTER=true >WITHOUT_CASE_FILTER_IN=true >WITHOUT_EXT_FILTER=true >WITHOUT_LOG_FORENSIC=true >WITHOUT_OPTIONAL_HOOK_EXPORT=true >WITHOUT_OPTIONAL_HOOK_IMPORT=true >WITHOUT_OPTIONAL_FN_IMPORT=true >WITHOUT_OPTIONAL_FN_EXPORT=true >WITHOUT_LDAP=true >WITHOUT_AUTHNZ_LDAP=true >WITH_ACTIONS=true >WITH_ALIAS=true >WITH_ASIS=true >WITH_AUTOINDEX=true >WITH_CERN_META=true >WITH_CGI=true >WITH_CHARSET_LITE=true >WITHOUT_DBD=true >WITH_DEFLATE=true >WITH_DIR=true >WITH_DUMPIO=true >WITH_ENV=true >WITH_EXPIRES=true >WITH_HEADERS=true >WITH_IMAGEMAP=true >WITH_INCLUDE=true >WITH_INFO=true >WITH_LOG_CONFIG=true >WITH_LOGIO=true >WITH_MIME=true >WITH_MIME_MAGIC=true >WITH_NEGOTIATION=true >WITH_REWRITE=true >WITH_SETENVIF=true >WITH_SPELING=true >WITH_STATUS=true >WITH_UNIQUE_ID=true >WITH_USERDIR=true >WITH_USERTRACK=true >WITH_VHOST_ALIAS=true >WITH_FILTER=true >WITH_VERSION=true >WITHOUT_PROXY=true >WITH_PROXY_CONNECT=true >WITH_PATCH_PROXY_CONNECT=true >WITHOUT_PROXY_FTP=true >WITHOUT_PROXY_HTTP=true >WITHOUT_PROXY_AJP=true >WITHOUT_PROXY_BALANCER=true >WITHOUT_PROXY_SCGI=true >WITH_SSL=true >WITHOUT_SUEXEC=true >WITHOUT_SUEXEC_RSRCLIMIT=true >WITH_REQTIMEOUT=true >WITHOUT_CGID=true > > And just for case output of of apr1 options file: > ># This file is auto-generated by 'make config'. ># No user-servicable parts inside! ># Options for apr-ipv6-devrandom-gdbm-db42-1.4.2.1.3.9_1 >_OPTIONS_READ=apr-ipv6-devrandom-gdbm-db42-1.4.2.1.3.9_1 >WITH_THREADS=true >WITH_IPV6=true >WITH_BDB=true >WITH_GDBM=true >WITHOUT_LDAP=true >WITHOUT_MYSQL=true >WITHOUT_NDBM=true >WITHOUT_PGSQL=true >WITHOUT_SQLITE=true >WITH_DEVRANDOM=true > > > As you see, threads are enabled in both, but still it shouldn't have any > effect on mod_cache, but only on mod_mem_cache, which is _disabled_. > > -- > Bartosz Stec > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Michael W. Lucasmwlu...@blackhelicopters.org http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ New book available: Network Flow Analysis http://www.networkflowanalysis.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
erroneous message from locked-up machine
I came in to work today to find one of my -current machines unable to open a pipe. (This probably had a lot to do with the spamd that went stark raving nutters overnight, but that's a separate problem.) A power cycle fixed the problem, but /var/log/messages was filled with: Nov 10 11:05:44 bewilderbeast kernel: kern.maxpipekva exceeded, please see tuning(7). Interesting. bewilderbeast~;sysctl kern.maxpipekva sysctl: unknown oid 'kern.maxpipekva' bewilderbeast~; And tuning(7) doesn't mention this, either. Is this just work-in-progress, or did someone forget to commit something? ==ml PS: Lesson of the day: no pipe KVA, no su. Great fun on remote machines! :-) -- Michael Lucas [EMAIL PROTECTED], [EMAIL PROTECTED] Today's chance of throwing it all away to start a goat farm: 41.8% http://www.BlackHelicopters.org/~mwlucas/ Absolute OpenBSD: http://www.AbsoluteOpenBSD.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bikeshed
On Fri, Sep 12, 2003 at 05:10:39AM +0200, Poul-Henning Kamp wrote: > Well, the reason I didn't answer until now was that I was eating some > sort of fish (species now forgotten). Sea bass. ==ml -- Michael Lucas [EMAIL PROTECTED], [EMAIL PROTECTED] Today's chance of throwing it all away to start a goat farm: 41.8% http://www.BlackHelicopters.org/~mwlucas/ Absolute OpenBSD: http://www.AbsoluteOpenBSD.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: breakage this morning
On Wed, Apr 02, 2003 at 06:53:22PM +0400, Maxim Konovalov wrote: > On 16:51+0200, Apr 2, 2003, Sheldon Hearn wrote: > > > On (2003/04/02 09:43), Michael W . Lucas wrote: > > > > > > You sure you didn't get caught in the middle of a cvsup mirror sync? I > > > > have an IP_EVIL world and kernel running fine here. > > > > > > According to some folks on IRC, it was renamed to "IP_EF" in > > > src/sys/netinet/ip.h, but not renamed in ping.c. > > > > > > I just finished re-supping from cvsup16, and while I got some updates, > > > an update to ping_c was not among them... > > > > Ah, so it's me who got lucky, not you who got unlucky. > > fixed. Thank you very much! ==ml -- Michael Lucas [EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ Absolute BSD: http://www.AbsoluteBSD.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: breakage this morning
On Wed, Apr 02, 2003 at 04:30:55PM +0200, Sheldon Hearn wrote: > On (2003/04/02 09:20), Michael W . Lucas wrote: > > > While I'm all for a sense of humor, and agree that implementation of > > the IP_EVIL flag is vital for FreeBSD to be a modern operating system, > > it stops being funny when it breaks world. > > You sure you didn't get caught in the middle of a cvsup mirror sync? I > have an IP_EVIL world and kernel running fine here. According to some folks on IRC, it was renamed to "IP_EF" in src/sys/netinet/ip.h, but not renamed in ping.c. I just finished re-supping from cvsup16, and while I got some updates, an update to ping_c was not among them... ==ml -- Michael Lucas [EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ Absolute BSD: http://www.AbsoluteBSD.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
breakage this morning
While I'm all for a sense of humor, and agree that implementation of the IP_EVIL flag is vital for FreeBSD to be a modern operating system, it stops being funny when it breaks world. ... ===> sbin/ping cc -O -pipe -march=pentiumpro -DIPSEC -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/sbin/ping/ping.c /usr/src/sbin/ping/ping.c: In function `main': /usr/src/sbin/ping/ping.c:605: `IP_EVIL' undeclared (first use in this function) /usr/src/sbin/ping/ping.c:605: (Each undeclared identifier is reported only once /usr/src/sbin/ping/ping.c:605: for each function it appears in.) /usr/src/sbin/ping/ping.c: In function `pr_pack': /usr/src/sbin/ping/ping.c:1004: `IP_EVIL' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/sbin/ping. ... ==ml -- Michael Lucas [EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ Absolute BSD: http://www.AbsoluteBSD.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
unrecognized Prism III card
Hi folks, I picked up a couple of no-name Prism III cards, and found that FreeBSD-current doesn't recognize them. Is there anything I can do to make these work? (Up to and including shipping a card to a committer?) Mar 27 07:14:35 pedicular kernel: pccard1: (manufacturer=0x50c2, product=0x7300) at function 0 Mar 27 07:14:35 pedicular kernel: pccard1:CIS info: WLAN, PRISM PCMCIA CARD, 37300P Thanks, ==ml -- Michael Lucas [EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ Absolute BSD: http://www.AbsoluteBSD.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
