[Bug 275632] process being killed which has a big file mmap'ed and performs writes to it

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275632 --- Comment #5 from Martin Birgmeier --- Update: Not only the program itself but also unrelated programs may be killed - here is an excerpt of today's /var/log/messages: Jan 3 09:08:55 hal kernel: pid 4892 (cawic), jid 0, uid 20201, was k

[Bug 275632] process being killed which has a big file mmap'ed and performs writes to it

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275632 --- Comment #6 from Martin Birgmeier --- Output of "vmstat -c 1000" just before the program gets killed: procsmemorypage disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 in

[Bug 276092] "route add 10/8 ip" adds 0.0.0.0/8, not 10.0.0.0/8

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276092 Marek Zarychta changed: What|Removed |Added CC||zarych...@plan-b.pwste.edu.

[Bug 276092] "route add 10/8 ip" adds 0.0.0.0/8, not 10.0.0.0/8

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276092 Mark Linimon changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 276092] "route add 10/8 ip" adds 0.0.0.0/8, not 10.0.0.0/8

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276092 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiv

[Bug 275632] process being killed which has a big file mmap'ed and performs writes to it

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275632 --- Comment #7 from Martin Birgmeier --- Watching the vmstat output, it seems that there is no pageout activity for a long time even while the cawic process has already started rewriting substantial amounts of the mapped file. Maybe the OS

[Bug 275632] process being killed which has a big file mmap'ed and performs writes to it

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275632 --- Comment #8 from Martin Birgmeier --- Another kill with associated vmstat output: 0 0 14 17G 333M 14K 0 434 0 15K 18K 0 0 1373 62K 34K 1 5 94 0 0 14 17G 335M 14K 0 422 0 15K 18K 0 0 1354 61K 33K 1 6 9

[Bug 275744] Sendmail will not make all restart

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275744 --- Comment #5 from Emanuel Haupt --- (In reply to Russell from comment #4) Thank you Russel. For the record, it's also mentioned in the 20221205 entry in /usr/src/UPDATING. -- You are receiving this mail because: You are the assignee fo

[Bug 209628] freebsd-update upgrade broken in jail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209628 Michael Osipov changed: What|Removed |Added CC||micha...@freebsd.org --- Comment

[Bug 209628] freebsd-update upgrade broken in jail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209628 --- Comment #4 from Michael Osipov --- This could be used, I guess: root@deblndw013x4v1j:~ # sysctl -a | grep jail .. security.jail.jailed: 1 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 253989] freebsd-update: workdir should default to ${basedir}/var/db/freebsd-update

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253989 --- Comment #1 from Michael Osipov --- Can we close this as dup of Bug 235318? The report is identical. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 276093] wc(1) fails to read files on pseudo-filesystems with the -c option

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276093 Bug ID: 276093 Summary: wc(1) fails to read files on pseudo-filesystems with the -c option Product: Base System Version: 14.0-STABLE Hardware: Any OS:

[Bug 276094] freebsd-update: -j/-b have incomplete/unclear semantics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276094 Bug ID: 276094 Summary: freebsd-update: -j/-b have incomplete/unclear semantics Product: Base System Version: 13.2-STABLE Hardware: Any OS: Any

[Bug 276094] freebsd-update: -j/-b have incomplete/unclear semantics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276094 --- Comment #1 from Michael Osipov --- This issue is visibible when using Bastille-managed jails: * https://github.com/BastilleBSD/bastille/blob/master/usr/local/share/bastille/upgrade.sh * https://github.com/BastilleBSD/bastille/blob/maste

[Bug 235318] when updating jails using -b, freebsd-update is reusing host's /var/db/freebsd-update without indication of doing so, unless explicit -d as well

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235318 Michael Osipov changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 276094] freebsd-update: -j/-b have incomplete/unclear semantics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276094 Michael Osipov changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 209628] freebsd-update upgrade broken in jail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209628 Michael Osipov changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 276094] freebsd-update: -j/-b have incomplete/unclear semantics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276094 Michael Osipov changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 253989] freebsd-update: workdir should default to ${basedir}/var/db/freebsd-update

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253989 Michael Osipov changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 276094] freebsd-update: -j/-b have incomplete/unclear semantics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276094 Michael Osipov changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 276094] freebsd-update: -j/-b have incomplete/unclear semantics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276094 Michael Osipov changed: What|Removed |Added URL||https://github.com/Bastille

[Bug 269767] VM IMAGES panic on boot under LXC / LXD

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269767 Mina Galić changed: What|Removed |Added Resolution|--- |FIXED Status|Open

[Bug 276043] md5(1) et al are broken when reading the last argument because of capsicum(4) code

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276043 --- Comment #9 from Ricardo Branco --- (In reply to Mark Johnston from comment #8) I tested the patch and it works. Please don't close this bug until https://github.com/freebsd/freebsd-src/pull/984#issuecomment-1874667265 is addressed. Ch

[Bug 276043] md5(1) et al are broken when reading the last argument because of capsicum(4) code

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276043 --- Comment #10 from Mark Johnston --- (In reply to Ricardo Branco from comment #9) Thanks! Do you plan to work on the md5 issue? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 276043] md5(1) et al are broken when reading the last argument because of capsicum(4) code

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276043 --- Comment #11 from Ricardo Branco --- (In reply to Mark Johnston from comment #10) Yes. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 276099] freebsd-update: manpage does not mention '-v' option and its aliases

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276099 Bug ID: 276099 Summary: freebsd-update: manpage does not mention '-v' option and its aliases Product: Base System Version: 15.0-CURRENT Hardware: Any

[Bug 209628] freebsd-update upgrade broken in jail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209628 --- Comment #5 from Leif Pedersen --- I guess I don't see the point of examining sysctl or branching differently when in a jail. There's actually no need for `freebsd-update` to be aware of jails at all, nor be aware of the currently runnin

[Bug 209628] freebsd-update upgrade broken in jail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209628 --- Comment #6 from Michael Osipov --- (In reply to Leif Pedersen from comment #5) Agree, no reason to use uname here. freebsd-version everywhere. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 276101] Cannot build world for 14-stable

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276101 Bug ID: 276101 Summary: Cannot build world for 14-stable Product: Base System Version: 14.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Aff

[Bug 276102] freebsd-update: command gives questionable recommendation which command to run next

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276102 Bug ID: 276102 Summary: freebsd-update: command gives questionable recommendation which command to run next Product: Base System Version: 13.2-STABLE Hardware: Any

[Bug 276043] md5(1) et al are broken when reading the last argument because of capsicum(4) code

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276043 --- Comment #12 from Ricardo Branco --- Hopefully fixed by https://github.com/freebsd/freebsd-src/pull/988 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 209628] freebsd-update upgrade broken in jail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209628 Xin LI changed: What|Removed |Added Assignee|b...@freebsd.org|sect...@freebsd.org CC|

[Bug 276106] hexdump(1) is not able to skip on files residing on pseudo-filesystems

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276106 Bug ID: 276106 Summary: hexdump(1) is not able to skip on files residing on pseudo-filesystems Product: Base System Version: 14.0-STABLE Hardware: Any

[Bug 276107] tail(1) is not able to operate on files residing in pseudo-filesystems

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276107 Bug ID: 276107 Summary: tail(1) is not able to operate on files residing in pseudo-filesystems Product: Base System Version: 14.0-STABLE Hardware: Any

[Bug 276107] tail(1) is not able to operate on files residing in pseudo-filesystems

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276107 Mina Galić changed: What|Removed |Added CC||free...@igalic.co Status|

[Bug 276106] hexdump(1) is not able to skip on files residing on pseudo-filesystems

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276106 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #1 f

[Bug 276106] hexdump(1) is not able to skip on files residing on pseudo-filesystems

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276106 Xin LI changed: What|Removed |Added CC||delp...@freebsd.org --- Comment #2 from X

[Bug 276106] hexdump(1) is not able to skip on files residing on pseudo-filesystems

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276106 --- Comment #3 from Mark Johnston --- (In reply to Xin LI from comment #2) Does the performance consideration really matter in practice given that these files are typically quite small. I didn't know that /proc files in Linux have size 0 t

[Bug 253989] freebsd-update: workdir should default to ${basedir}/var/db/freebsd-update

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253989 Mark Linimon changed: What|Removed |Added Resolution|--- |DUPLICATE Status|New

[Bug 235318] when updating jails using -b, freebsd-update is reusing host's /var/db/freebsd-update without indication of doing so, unless explicit -d as well

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235318 Mark Linimon changed: What|Removed |Added CC||asom...@freebsd.org --- Comment #1

[Bug 276106] hexdump(1) is not able to skip on files residing on pseudo-filesystems

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276106 --- Comment #4 from Ricardo Branco --- (In reply to Xin LI from comment #2) The GNU tools expect this behaviour and adapt accordingly. -- You are receiving this mail because: You are the assignee for the bug.