[Bug 254159] Keepalive not working/tcp rst tolerance

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254159

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254177] When ZFS is recognized, An i386 machine with a lot of memory hangs.

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254177

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|f...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254177] When ZFS is recognized, An i386 machine with a lot of memory hangs.

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254177

Bug ID: 254177
   Summary: When ZFS is recognized, An i386 machine with a lot of
memory hangs.
   Product: Base System
   Version: 13.0-STABLE
  Hardware: i386
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: btren...@yahoo.co.jp

When ZFS is recognized, An i386 machine with a lot of memory hangs on FreeBSD
13.0-RC1 (git 60e8939aa85b07f3271dcc01730727dda04c8bf6).

It  occurs on line 799th of /usr/src/sys/contrib/openzfs/module/zfs/dbuf.c 

while (hsize * zfs_arc_average_blocksize < physmem * PAGESIZE)
hsize <<= 1;

My machine has 24GB of memory,  so `physmem' is 0x59B9AD and `PAGESIZE' is
0x1000, but `physmem * PAGESIZE'  overflows to 0x9B9AD000.  Then the condition
of the while statement may always be true, and this statement goes into an
eternal loop.



To fix that immediately, that line will be changed to

while (hsize * zfs_arc_average_blocksize < (uint64_t)physmem *
PAGESIZE)

or

while (hsize / PAGESIZE * zfs_arc_average_blocksize < physmem)

On the other hand, that problem comes from the type of the variable `physmem'
which is declared on line 65th of /usr/src/sys/sys/systm.h for kernel,

extern long physmem;/* physical memory */

and on line 54th of  /usr/src/sys/contrib/openzfs/lib/libzpool/kernel.c for
userland.

uint64_t physmem;

That problem does not occur on amd64, because the sizeof(long) is different.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 251363] use unionfs as a disk-cache for NFS [feature]

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251363

Wayne Willcox  changed:

   What|Removed |Added

 CC||wwillc...@gmail.com

--- Comment #17 from Wayne Willcox  ---
Looks pretty interesting to me I was just looking for a way to cache files from
nfs.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240122] ddb: cont doesn't give a working terminal back

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240122

Mitchell Horne  changed:

   What|Removed |Added

 Status|Open|In Progress
 CC||mho...@freebsd.org
URL||https://reviews.freebsd.org
   ||/D29130
   Assignee|b...@freebsd.org|mho...@freebsd.org

--- Comment #5 from Mitchell Horne  ---
FYI, I believe I've tracked down this issue, and posted a fix to
https://reviews.freebsd.org/D29130

I plan to commit in the next day or two, but if anyone else can verify that
this fixes the issue for them it would be helpful.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254146] gmirror does not create a mirror or silently truncates its name

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254146

--- Comment #2 from ras...@superbox.pl ---
(In reply to Robert Wing from comment #1)

I am agree with everything.

Additionally, it should be documented that the restriction also applies to
provider type, in my case gpt/ which means 4 characters less for the provider
name.

That is why I was unable to hardcode GPT label longer than 11 characters.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254174] pkgbase: uninstalling dbg or other variants of "vital" packages is impossible

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254174

Bug ID: 254174
   Summary: pkgbase: uninstalling dbg or other variants of "vital"
packages is impossible
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: m...@igalic.co

meena@beastix ~> sudo pkg remove FreeBSD-utilities-dbg-lib32
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages
in the universe):

Installed packages to be REMOVED:
FreeBSD-utilities-dbg-lib32: 14.snap20210306210736

Number of packages to be removed: 1

The operation will free 26 MiB.

Proceed with deinstalling packages? [y/N]: y
pkg: Cannot delete vital package: FreeBSD-utilities-dbg-lib32!
pkg: If you are sure you want to remove FreeBSD-utilities-dbg-lib32,
pkg: unset the 'vital' flag with: pkg set -v 0 FreeBSD-utilities-dbg-lib32
meena@beastix ~ [3]>

i do not consider -dbg packages vital
heck, i don't think i'd consider lib32 packages vital!

most, if not all packages we split off from vital packages can be marked as
non-vital

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254171] 13.0-RC1: pf: vnet: jail leaves a unnecessary swi1 thread in intr process

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254171

Bug ID: 254171
   Summary: 13.0-RC1: pf: vnet: jail leaves a unnecessary swi1
thread in intr process
   Product: Base System
   Version: 13.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: ras...@superbox.pl

To reproduce the issue you must load pf module and create the jail with vnet
option.

# cat /etc/jail.conf
path = "/usr/jail/${name}";
exec.clean;
exec.prestart   = "ifconfig epair${epairid} create";
exec.prestart  += "ifconfig epair${epairid}a inet6 ifdisabled up";
exec.prestart  += "ifconfig bridge0 addm epair${epairid}a";
exec.created= "cpuset -l 1 -j ${name}";
exec.start  = "ifconfig epair${epairid}b ether 02:ef:a4:c1:60:0${epairid}";
exec.start += "ifconfig epair${epairid}b inet ${ipaddress} netmask
${netmask}";
exec.start += "route add default ${gateway}";
exec.start += "sh /etc/rc";
exec.stop   = "sh /etc/rc.shutdown jail";
exec.poststop   = "ifconfig epair${epairid}a destroy";
host.hostname   = "${name}";
mount.devfs;
vnet;
vnet.interface  = "epair${epairid}b";
test1 {
$epairid= 1;
$ipaddress  = 192.168.0.101;
$netmask= 255.255.255.0;
$gateway= 192.168.0.1;
}
test2 {
$epairid= 2;
$ipaddress  = 192.168.0.102;
$netmask= 255.255.255.0;
$gateway= 192.168.0.1;
}

# ifconfig bridge0 create
# kldload pf
# service jail onestart
Starting jails: test1 test2.
# procstat -t 12 | egrep 'PID|swi1'
  PIDTID COMMTDNAME  CPU  PRI STATE   WCHAN
   12 100031 intrswi1: netisr 0   -1   28 wait-
   12 100134 intrswi1: pf send-1   28 wait-
   12 100138 intrswi1: pf send-1   28 wait-
   12 100147 intrswi1: pf send-1   28 wait-
# service jail onerestart
Stopping jails: test1 test2.
Starting jails: test1 test2.
# service jail onerestart
Stopping jails: test1 test2.
Starting jails: test1 test2.
# service jail onestop
Stopping jails: test1 test2.
# procstat -t 12 | egrep 'PID|swi1'
  PIDTID COMMTDNAME  CPU  PRI STATE   WCHAN
   12 100031 intrswi1: netisr 0   -1   28 wait-
   12 100134 intrswi1: pf send-1   28 wait-
   12 100138 intrswi1:-1   47 wait-
   12 100147 intrswi1:-1   47 wait-
   12 100157 intrswi1:-1   47 wait-
   12 100158 intrswi1:-1   47 wait-
   12 100159 intrswi1:-1   47 wait-
   12 100160 intrswi1:-1   47 wait-

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254092] libc: Please implement get_current_dir_name()

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254092

--- Comment #4 from Robert Wing  ---
(In reply to Robert Wing from comment #3)

not me, but you Tobias

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254092] libc: Please implement get_current_dir_name()

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254092

Robert Wing  changed:

   What|Removed |Added

 CC||r...@freebsd.org

--- Comment #3 from Robert Wing  ---
(In reply to Tobias Kortkamp from comment #2)

might consider making a review on phabricator for this..

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254146] gmirror does not create a mirror or silently truncates its name

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254146

Robert Wing  changed:

   What|Removed |Added

 CC||r...@freebsd.org

--- Comment #1 from Robert Wing  ---
(In reply to rashey from comment #0)

issue 1: 

As it is, the hardcoded value has a limit of 15 characters (as limited by the
current metadata format)..this restriction extends to the providers name as
well (only when hardcoding the name into the metadata though).

At the very least, this restriction should be documented. And maybe gmirror
should print an error when hardcoding a providers name that's longer than
hardcoded limit.

issue 2:

Similar problem here, the limit for a mirror name is 15 characters, also
limited by the current metadata format. That's why the mirror name gets
truncated.

This should also be documented. And possibly, gmirror should print error when
trying to create mirror with a name longer than the mirror limit?

If there's any input/feedback on how gmirror should behave when encountering
issue 1 and 2, would be worth hearing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 253942] clang -gz=zlib does not pass --compress-debug-sections to linker

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253942

Ed Maste  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED
   Assignee|b...@freebsd.org|ema...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254159] Keepalive not working/tcp rst tolerance

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254159

Bug ID: 254159
   Summary: Keepalive not working/tcp rst tolerance
   Product: Base System
   Version: 12.2-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: ant_m...@inbox.ru

OS: 12.2-STABLE r368657 GENERIC  amd64

I've ecnountered reproduceable problem with keepalive connection probes which
tolerate TCP RST response.

There is a connection between user application (client) and database (RDBMS) on
FreeBSD server. After killing user application the connection is still alive
(observed by netstat -x) on server.

The keepalive timer for the connection (initially set to net.inet.tcp.keepidle
value) is counting down. When it comes to zero, server send a keepalive probe.
Client response with TCP RST packet. Then connection on server is still alive
but keepalive timer resetted to net.inet.tcp.keepintvl value. After expiration
of this interval server do not send any packet but reset keepalive timer of
connection back to the net.inet.tcp.keepidle value. Then the things loop
forever.

P.S.
There is no firewall. 
It is proofed that server recieves TCP RST from client (visible with tcp dump).
RDBMS is  running in jail.

TCPdump from client:

193.017688000   192.168.0.3 192.168.0.2 TCP 66  3050→3583 [ACK]
Seq=1 Ack=1 Win=1026 Len=0
193.017816000   192.168.0.2 192.168.0.3 TCP 54  3583→3050 [RST]
Seq=1 Win=0 Len=0
1093.033029000  192.168.0.3 192.168.0.2 TCP 66  [TCP Dup ACK
5#1] 3050→3583 [ACK] Seq=1 Ack=1 
1093.033154000  192.168.0.2 192.168.0.3 TCP 54  3583→3050 [RST]
Seq=1 Win=0 Len=0
1993.113115000  192.168.0.3 192.168.0.2 TCP 66  [TCP Dup ACK
5#2] 3050→3583 [ACK] Seq=1 Ack=1 
1993.113245000  192.168.0.2 192.168.0.3 TCP 54  3583→3050 [RST]
Seq=1 Win=0 Len=0
...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 253942] clang -gz=zlib does not pass --compress-debug-sections to linker

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253942

--- Comment #5 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=c4dbe899aa08f60b66426ecf63b1346bffe25ed8

commit c4dbe899aa08f60b66426ecf63b1346bffe25ed8
Author: Ed Maste 
AuthorDate: 2021-03-03 01:35:57 +
Commit: Ed Maste 
CommitDate: 2021-03-09 14:28:54 +

clang: Fix -gz=zlib options for linker

Clang commit ccb4124a4172bf2cb2e1cd7c253f0f1654fce294:

Fix -gz=zlib options for linker

gcc translates -gz=zlib to --compress-debug-options=zlib for both
assembler and linker but clang only does this for assembler.

The linker needs --compress-debug-options=zlib option to compress the
debug sections in the generated executable or shared library.

Due to this bug, -gz=zlib has no effect on the generated executable or
shared library.

This patch fixes that.

Clang commit 462cf39a5c180621b56f7602270ce33eb7b68d23:

[Driver] Fix -gz=zlib options for linker also on FreeBSD

ccb4124a4172 fixed translating -gz=zlib to --compress-debug-sections for
linker invocation for several ToolChains, but omitted FreeBSD.

PR: 253942
Approved by:dim
Sponsored by:   The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D29028

(cherry picked from commit 19587d742264c5caec33d218e9cea6eb78f6c6bb)

 .../clang/lib/Driver/ToolChains/AMDGPU.cpp |  1 +
 .../clang/lib/Driver/ToolChains/CommonArgs.cpp | 18 ++
 .../clang/lib/Driver/ToolChains/CommonArgs.h   |  4 
 .../clang/lib/Driver/ToolChains/FreeBSD.cpp|  1 +
 .../llvm-project/clang/lib/Driver/ToolChains/Gnu.cpp   |  1 +
 .../llvm-project/clang/lib/Driver/ToolChains/HIP.cpp   |  2 ++
 6 files changed, 27 insertions(+)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027
Bug 231027 depends on bug 253754, which changed state.

Bug 253754 Summary: growfs(8): Fails to resize with 13.0-BETA3: "is not clean - 
run fsck."
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253754

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 238003] freebsd-update fetch metadata failed

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238003

Dag-Erling Smørgrav  changed:

   What|Removed |Added

 CC||d...@freebsd.org
 Resolution|--- |Not A Bug
 Status|Open|Closed

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 247155] unbound-checkconf fails because default path /etc/unbound is hardcoded and FreeBSD uses /var/unbound instead

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247155

Dag-Erling Smørgrav  changed:

   What|Removed |Added

 Status|New |Open
   Assignee|b...@freebsd.org|d...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 248010] 'make buildworld': unbound build failure on 12.1-RELEASE-p7

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248010

Dag-Erling Smørgrav  changed:

   What|Removed |Added

 CC||d...@freebsd.org
 Status|Open|Closed
 Resolution|--- |Works As Intended

--- Comment #16 from Dag-Erling Smørgrav  ---
This is a support issue, not a bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 250984] local-unbound-setup does not work with ipv6 forwarders without "::" in address

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250984

Dag-Erling Smørgrav  changed:

   What|Removed |Added

 Status|New |In Progress
   Assignee|b...@freebsd.org|d...@freebsd.org
 CC||d...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 250984] local-unbound-setup does not work with ipv6 forwarders without "::" in address

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250984

--- Comment #5 from Patrick M. Hausen  ---
Created attachment 223114
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223114=edit
Fixed patch to /usr/sbin/local-unbound-setup

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 250984] local-unbound-setup does not work with ipv6 forwarders without "::" in address

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250984

--- Comment #4 from Patrick M. Hausen  ---
Sorry - messed it up. The proposed patch now only works if there is *no* '::'
in the address. Uploading a fixed one.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 250984] local-unbound-setup does not work with ipv6 forwarders without "::" in address

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250984

--- Comment #3 from Patrick M. Hausen  ---
Hey folks,

I attached a patch - please give this a higher priority. I just wasted half a
working day searching for a problem in my Ansible code until I found that
local-unbound-setup is broken and finally this bug report.

Global unicast addresses do not in general contain the string '::' ;-)

Kind regards,
Patrick

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 250984] local-unbound-setup does not work with ipv6 forwarders without "::" in address

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250984

Patrick M. Hausen  changed:

   What|Removed |Added

 CC||p...@hausen.com

--- Comment #2 from Patrick M. Hausen  ---
Created attachment 223112
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223112=edit
Patch to /usr/sbin/local-unbound-setup

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 254092] libc: Please implement get_current_dir_name()

2021-03-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254092

--- Comment #2 from Tobias Kortkamp  ---
I've tried to do this here:
https://github.com/t6/freebsd-src/tree/get_current_dir_name

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"