[Bug 202127] First login slow repsonse
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202127 Bug ID: 202127 Summary: First login slow repsonse Product: Base System Version: 10.1-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Many People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: are.engebraa...@gmail.com Immediately after boot (without x) there is a "Login:" prompt. If I write my username, return and start typing my password directly, part of it will show and not get registered as part of the password. For example, I can easily type "asdf[RETURN]asdf[RETURN]" before "Password:" comes up. My machine is just a cheap old testmachine, 2Ghz T61 Thinkpad, but still this kind of thing should be doable much faster than I can type one character. Btw, after one attempt at login the speed is quite fast enough that I cannot do this anymore. A random guy on IRC said he had the same issue, which leads me to think this is universal. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202127] First login slow repsonse
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202127 --- Comment #1 from s00pern00ber --- Output of uname -a FreeBSD 10.1-RELEASE-p16 FreeBSD 10.1-RELEASE-p16 #0: Tue Jul 28 11:41:12 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202130] Sysctl kern.racct.enable=1 in /boot/loader.conf has no affect on 10.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202130 Bug ID: 202130 Summary: Sysctl kern.racct.enable=1 in /boot/loader.conf has no affect on 10.2 Product: Base System Version: 10.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: dominik.za...@baycix.de If you set the kern.racct.enable=1 variable in 10.2 it has no affect. This leads to a not working rctl. We tested with RC1 on physical server and RC2 as virtual machine both with amd64 images. On both systems the rctl reports that kern.racct.enable=1 is not set correctly. With 11-Current as a virutal machine this bug does not appear, there it works as expected. We followed the steps mentioned in https://www.freebsd.org/releases/10.2R/relnotes.html section 5.3 Workaround is to rebuild the kernel: Remove the "options RACCT_DEFAULT_TO_DISABLED" from the config got it working with 10.2 RC2. But this sysctl is designed that you are not forced to rebuild the kernel. I am happy to help reproducing or testing this. Regards, Dominik -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202130] Sysctl kern.racct.enable=1 in /boot/loader.conf has no affect on 10.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202130 Kubilay Kocak changed: What|Removed |Added Keywords||needs-patch, needs-qa, ||regression CC||r...@freebsd.org Flags||mfc-stable10? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202130] Sysctl kern.racct.enable=1 in /boot/loader.conf has no affect on 10.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202130 Glen Barber changed: What|Removed |Added Status|New |Closed Resolution|--- |FIXED --- Comment #1 from Glen Barber --- This is fixed in stable/10 and releng/10.2 for inclusion in -RC3. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202135] nscd does not accept a value of zero for negative-time-to-live for passwd nor group
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202135 Bug ID: 202135 Summary: nscd does not accept a value of zero for negative-time-to-live for passwd nor group Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: trond.endres...@ximalas.info System is FreeBSD/i386, stable/10, r286362. This config is acceptable by nscd: threads 8 enable-cachepasswd yes positive-time-to-live passwd 600 negative-time-to-live passwd 1 check-files passwd no enable-cachegroup yes positive-time-to-live group 3600 negative-time-to-live group 1 check-files group no This config is NOT acceptable by nscd: threads 8 enable-cachepasswd yes positive-time-to-live passwd 600 negative-time-to-live passwd 0 check-files passwd no enable-cachegroup yes positive-time-to-live group 3600 negative-time-to-live group 0 check-files group no nscd simply dies with the latter configuration, although this gets logged: Aug 6 15:45:35 hostname kernel: pid 730 (nscd), uid 0: exited on signal 6 (core dumped) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202127] Initial (first) login response is slow/delayed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202127 Kubilay Kocak changed: What|Removed |Added Keywords||needs-qa Summary|First login slow repsonse |Initial (first) login ||response is slow/delayed -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 201992] [panic] Fatal trap 12: page fault while in kernel mode sysctl -a|grep debug.vmem_check
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201992 --- Comment #1 from Ivan Klymenko --- nonamehost.local dumped core - see /var/crash/vmcore.1 Thu Aug 6 19:48:42 EEST 2015 FreeBSD nonamehost.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r286317: Wed Aug 5 17:42:31 EEST 2015 ivan@nonamehost.local:/media/da0s1/obj/usr/src/sys/mk11 amd64 panic: page fault 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"... Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fault virtual address= 0x6776732edc fault code= supervisor write data, page not present instruction pointer= 0x20:0x80ad4e8c stack pointer= 0x28:0xfe01a9ce0650 frame pointer= 0x28:0xfe01a9ce06a0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= resume, IOPL = 0 current process= 35076 (sysctl) trap number= 12 panic: page fault cpuid = 2 KDB: stack backtrace: #0 0x80ac0227 at kdb_backtrace+0x67 #1 0x80a7c1b9 at vpanic+0x189 #2 0x80a7c023 at panic+0x43 #3 0x80f50ee5 at trap_fatal+0x355 #4 0x80f51226 at trap_pfault+0x326 #5 0x80f50884 at trap+0x464 #6 0x80f34e22 at calltrap+0x8 #7 0x80a5d456 at __mtx_lock_sleep+0xc6 #8 0x80dbf950 at uma_zone_get_cur+0x70 #9 0x80dc18d9 at sysctl_handle_uma_zone_cur+0x19 #10 0x80a89e6a at sysctl_root_handler_locked+0x17a #11 0x80a8950d at sysctl_root+0x21d #12 0x80a89ae0 at userland_sysctl+0x260 #13 0x80a89844 at sys___sysctl+0x74 #14 0x80f51944 at amd64_syscall+0x3f4 #15 0x80f3510b at Xfast_syscall+0xfb Uptime: 7h57m2s Dumping 1071 out of 6043 MB:..2%..11%..21%..32%..41%..51%..62%..71%..81%..92% Reading symbols from /bootpool/boot/kernel/fdescfs.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/fdescfs.ko.symbols Reading symbols from /bootpool/boot/kernel/linprocfs.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/linprocfs.ko.symbols Reading symbols from /bootpool/boot/kernel/linux_common.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/linux_common.ko.symbols Reading symbols from /bootpool/boot/kernel/linsysfs.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/linsysfs.ko.symbols Reading symbols from /bootpool/boot/kernel/zfs.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/zfs.ko.symbols Reading symbols from /bootpool/boot/kernel/opensolaris.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/opensolaris.ko.symbols Reading symbols from /bootpool/boot/kernel/coretemp.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/coretemp.ko.symbols Reading symbols from /bootpool/boot/kernel/ichwd.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/ichwd.ko.symbols Reading symbols from /bootpool/boot/kernel/cpuctl.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/cpuctl.ko.symbols Reading symbols from /bootpool/boot/kernel/aesni.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/aesni.ko.symbols Reading symbols from /bootpool/boot/kernel/cryptodev.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/cryptodev.ko.symbols Reading symbols from /bootpool/boot/kernel/sem.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/sem.ko.symbols Reading symbols from /bootpool/boot/kernel/accf_data.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/accf_data.ko.symbols Reading symbols from /bootpool/boot/kernel/accf_http.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/accf_http.ko.symbols Reading symbols from /bootpool/boot/kernel/accf_dns.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/accf_dns.ko.symbols Reading symbols from /bootpool/boot/kernel/h_ertt.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/h_ertt.ko.symbols Reading symbols from /bootpool/boot/kernel/cc_dctcp.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/cc_dctcp.ko.symbols Reading symbols from /bootpool/boot/kernel/cc_cdg.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/cc_cdg.ko.symbols Reading symbols from /bootpool/boot/kernel/cc_chd.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/cc_chd.ko.symbols Reading symbols from /bootpool/boot/kernel/cc_cubic.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/cc_cubic.ko.symbols Reading symbols from /bootpool/boot/kernel/cc_hd.ko.symbols...done. Loaded symbols for /bootpool/boot/kernel/cc_hd.ko.symbols Reading sy
[Bug 202111] Core dumped in pw usermod
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202111 Xin LI changed: What|Removed |Added CC||delp...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|b...@freebsd.org --- Comment #5 from Xin LI --- Assign this to bapt@ who have created the fix for completeness (please ignore: this is already addressed in the affected releng/10.2 branch). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202140] HP Z600 defaults to LAPIC for kern.eventtimer.timer but can't use 'Online CPU idle state' higher than C1 with this setting
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202140 Bug ID: 202140 Summary: HP Z600 defaults to LAPIC for kern.eventtimer.timer but can't use 'Online CPU idle state' higher than C1 with this setting Product: Base System Version: 10.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: bre...@gmail.com This computer is comsuming 160 watt when idle. I was looking for a way to reduce that and was told to set 'hw.acpi.cpu.cx_lowest' to 'C3' or 'C8'. If I'm setting 'hw.acpi.cpu.cx_lowest' to anything else than 'C1' the system stops working properly. Applications just stop - waiting forever. This can very easily be reproduced with ping. Starting to type anything on the shell "wakes" the computer up and applications start to respond and work again. A clean reboot is not possible with these settings. Default for this computer for 'kern.eventtimer.timer' is 'LAPIC'. Allan Jude from BSD Now, who was guiding me through the whole process, told me to try 'HPET', which worked. Both 'C3' and 'C8' for 'hw.acpi.cpu.cx_lowest' are now possible without any downside effects. Power consumption is down to around 90 watt with 'C8' and the system is working flawlessly and stable. Thanks Allan, Kris and last but not least TJ! But it would be much nicer, if this would work right out of the box! Some additional information: --- Xeon E5520 --- $ sysctl hw.|head hw.machine: amd64 hw.model: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz hw.ncpu: 8 hw.byteorder: 1234 hw.physmem: 8545079296 hw.usermem: 8300666880 hw.pagesize: 4096 hw.floatingpoint: 1 hw.machine_arch: amd64 hw.realmem: 8592031744 --- Event timer choices --- $ sysctl kern.eventtimer.choice kern.eventtimer.choice: LAPIC(400) HPET(350) HPET1(340) HPET2(340) HPET3(340) i8254(100) RTC(0) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202141] libzfs.so: Undefined symbol "uu_avl_pool_create" when using java
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202141 Bug ID: 202141 Summary: libzfs.so: Undefined symbol "uu_avl_pool_create" when using java Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: nnew...@tag1consulting.com Hello All, I am currently working on a large jenkins/hudson deployment with FreeBSD 10.1 + ZFS as the base. Under load, jenkins (java) crashes with the following in the log: /usr/lib/libzfs.so: Undefined symbol "uu_avl_pool_create" Looking around, I see that this symbol is defined in libuutil. This looks like a very similar issue to bug 183081 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183081). Similar to that, when looking at illumos (https://github.com/joyent/illumos-joyent/blob/master/usr/src/lib/libzfs/Makefile.com) libzfs is linked against libuutil, but the FreeBSD version doesn't appear to be (unless I am entirely blind, which is always possible). I can fix this by pre-loading libuutil, but I wanted to open a bug about this so that it could be fixed similar to 183081. Thanks! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202142] Uninitialized variable usage in error path in _dns_getaddrinfo()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202142
Bug ID: 202142
Summary: Uninitialized variable usage in error path in
_dns_getaddrinfo()
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: misc
Assignee: freebsd-bugs@FreeBSD.org
Reporter: se...@cosemica.com
The calls to RES_SET_H_ERRNO() macro on error paths wind up
dereferencing an uninitialized res:
Index: net/getaddrinfo.c
===
--- net/getaddrinfo.c(revision 286381)
+++ net/getaddrinfo.c(working copy)
@@ -2154,6 +2154,8 @@
memset(&sentinel, 0, sizeof(sentinel));
cur = &sentinel;
+res = __res_state();
+
buf = malloc(sizeof(*buf));
if (!buf) {
RES_SET_H_ERRNO(res, NETDB_INTERNAL);
@@ -2200,7 +2202,6 @@
return NS_UNAVAIL;
}
-res = __res_state();
if ((res->options & RES_INIT) == 0 && res_ninit(res) == -1) {
RES_SET_H_ERRNO(res, NETDB_INTERNAL);
free(buf);
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 201588] [PATCH] make pkill/pgrep -j ARG take jname, not just jid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201588 danie...@apache.org changed: What|Removed |Added CC||danie...@apache.org --- Comment #1 from danie...@apache.org --- Created attachment 159627 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159627&action=edit patch, v2 Attached an updated patch: v2 is like v1 but with an updated comment in the tests. Reviewed by brd@. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202144] Routing stops working when we create a new vlan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 Bug ID: 202144 Summary: Routing stops working when we create a new vlan Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: gon...@bsdinfo.com.br Let me illustrate a network topology, to tell where the problem occurs: PC station: 192.168.8.253/24 (FreeBSD 10.2-PRERELEASE) Router: 192.168.8.177/24 and 10.254.215.1/24 (FreeBSD 10.2-RC2) router(CPE): 10.254.215.188/24 (a customer) >From Router: === # ifconfig vlan201 vlan201: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.215.1 netmask 0xff00 broadcast 10.254.215.255 inet6 fe80::7271:bcff:fe87:312d%vlan201 prefixlen 64 scopeid 0x1a nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 201 parent interface: em0 >From PC station (192.168.8.253): === # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes 64 bytes from 10.254.215.188: icmp_seq=0 ttl=127 time=1.012 ms 64 bytes from 10.254.215.188: icmp_seq=1 ttl=127 time=0.864 ms 64 bytes from 10.254.215.188: icmp_seq=2 ttl=127 time=1.084 ms 64 bytes from 10.254.215.188: icmp_seq=3 ttl=127 time=1.618 ms 64 bytes from 10.254.215.188: icmp_seq=4 ttl=127 time=1.006 ms --- 10.254.215.188 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.864/1.117/1.618/0.261 ms It works perfectly. Now I'm going on the router and I just create a new vlan 202. >From Router: === # ifconfig vlan202 create # At that moment my PC station stops to ping the IP 10.254.215.188. >From PC station (192.168.8.253): === # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes --- 10.254.215.188 ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss For all work again I need to restart the router. I don't know if I could correctly explain the problem. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202146] unneeded zero of variables in elftoolchain 'size' program
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202146 Bug ID: 202146 Summary: unneeded zero of variables in elftoolchain 'size' program Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: l...@pix.net Created attachment 159629 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159629&action=edit Patch to remove unneeded variable setting in 'size' program. There's an unnecessary zeroing of two variables in the 'size' program. Pointed out by the clang static analysis tool. I've been running with this patch for a couple of months on my machine that tracks -CURRNET and have noticed no problems. Patch is attached. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202144] Routing stops working when we create a new vlan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 --- Comment #1 from gon...@bsdinfo.com.br --- ifconfig and netstat before new vlan: = # ifconfig em0: flags=8843 metric 0 mtu 1500 options=4219b ether 70:71:bc:87:31:2d inet6 fe80::7271:bcff:fe87:312d%em0 prefixlen 64 tentative scopeid 0x1 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active em1: flags=8843 metric 0 mtu 1500 options=4219b ether 00:1b:21:9d:48:e8 inet 192.168.8.177 netmask 0xff00 broadcast 192.168.8.255 inet6 fe80::21b:21ff:fe9d:48e8%em1 prefixlen 64 tentative scopeid 0x2 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active pflog0: flags=141 metric 0 mtu 33160 pfsync0: flags=0<> metric 0 mtu 1500 syncpeer: 0.0.0.0 maxupd: 128 defer: off lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet 127.0.0.1 netmask 0xff00 nd6 options=21 vlan2: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.253.1 netmask 0xff00 broadcast 10.254.253.255 inet6 fe80::7271:bcff:fe87:312d%vlan2 prefixlen 64 scopeid 0x6 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 2 parent interface: em0 vlan3: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.252.1 netmask 0xff00 broadcast 10.254.252.255 inet6 fe80::7271:bcff:fe87:312d%vlan3 prefixlen 64 scopeid 0x7 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 3 parent interface: em0 vlan4: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.251.1 netmask 0xff00 broadcast 10.254.251.255 inet6 fe80::7271:bcff:fe87:312d%vlan4 prefixlen 64 scopeid 0x8 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 4 parent interface: em0 vlan5: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.250.1 netmask 0xff00 broadcast 10.254.250.255 inet6 fe80::7271:bcff:fe87:312d%vlan5 prefixlen 64 scopeid 0x9 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 5 parent interface: em0 vlan6: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.249.1 netmask 0xff00 broadcast 10.254.249.255 inet6 fe80::7271:bcff:fe87:312d%vlan6 prefixlen 64 scopeid 0xa nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 6 parent interface: em0 vlan7: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.10.10.254 netmask 0xff00 broadcast 10.10.10.255 inet6 fe80::7271:bcff:fe87:312d%vlan7 prefixlen 64 scopeid 0xb inet 10.9.0.254 netmask 0xff00 broadcast 10.9.0.255 inet 10.9.1.254 netmask 0xff00 broadcast 10.9.1.255 inet 10.9.2.254 netmask 0xff00 broadcast 10.9.2.255 inet 10.9.3.254 netmask 0xff00 broadcast 10.9.3.255 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 7 parent interface: em0 vlan8: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.248.1 netmask 0xff00 broadcast 10.254.248.255 inet6 fe80::7271:bcff:fe87:312d%vlan8 prefixlen 64 scopeid 0xc inet 10.254.243.1 netmask 0xff00 broadcast 10.254.243.255 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 8 parent interface: em0 vlan9: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.254.248 netmask 0xff00 broadcast 10.254.254.255 inet6 fe80::7271:bcff:fe87:312d%vlan9 prefixlen 64 scopeid 0xd nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 9 parent interface: em0 vlan10: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.247.1 netmask 0xff00 broadcast 10.254.247.255 inet6 fe80::7271:bcff:fe87:312d%vlan10 prefixlen 64 scopeid 0xe nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 10 parent interface: em0 vlan11: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.246.1 netmask 0xff00 broadcast 10.254.246.255 inet6 fe80::7271:bcff:fe87:312d%vlan11 prefixlen 64 scopeid 0xf nd6 options=21 media: Ethernet
[Bug 202147] default listen queue in casperd is too small for some applications
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202147 Bug ID: 202147 Summary: default listen queue in casperd is too small for some applications Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: l...@pix.net Created attachment 159630 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159630&action=edit casperd queuelen patch, and man page fixes The current default listen queue for casperd is too small (8) and hard-coded. This patch increases the default to 16, and introduces a command line flag that can used to further increase or decrease the queue length. Patch is attached. The patch also documents the new option, and corrects the existing error in the man page where the command line options are listed twice. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 201588] [PATCH] make pkill/pgrep -j ARG take jname, not just jid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201588 Kubilay Kocak changed: What|Removed |Added Keywords||easy, feature, needs-qa -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202144] Routing stops working when we create a new vlan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 --- Comment #2 from gon...@bsdinfo.com.br --- All VLANs stop working when I create a new vlan. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
