https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264898
Bug ID: 264898
Summary: etc/rc.d/zfskeys should not reject valid keylocations
Product: Base System
Version: 13.1-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264904
Bug ID: 264904
Summary: /etc/rc.d/ntpd undefined variable:
$ntp_leapfile_fetch_opts
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264908
Bug ID: 264908
Summary: It does not work to obtain an IP address via DHCP
simultaneously for multiple interfaces
Product: Base System
Version: 12.3-STABLE
Hardware: a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218191
Vladislav V. Prodan changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264911
Bug ID: 264911
Summary: Error using installerconfig and PARTITIONS=DEFAULT on
VirtIO Device
Product: Base System
Version: 13.1-RELEASE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264911
--- Comment #1 from rsimmo...@gmail.com ---
Sorry, minor cut and paste error. that is a config for a slightly different VM
than the one I'm testing on. The difference is:
'net0': 'model=e1000,bridge=vmbr1'
is the following in the one I'm t
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #3 from d...@jetcafe.org ---
Created attachment 234961
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234961&action=edit
Past 3 months of activity
I've provided some more graphical data, graphing the actual sysctl
vm.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254763
--- Comment #16 from Mark Millard ---
(In reply to Mark Millard from comment #13 and #14)
poudriere-devel has gained:
# Grep build logs to determine a possible build failure reason. This is
# only shown on the web interface.
# Default: y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #4 from Bane Ivosev ---
Created attachment 234965
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234965&action=edit
monthly graph
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #5 from Bane Ivosev ---
Created attachment 234966
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234966&action=edit
daily graph
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #6 from Bane Ivosev ---
Comment on attachment 234965
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234965
monthly graph
In mid October we added RAM, then period with 12.3-RELEASE and you can see
exactly when we upgr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254763
Tatsuki Makino changed:
What|Removed |Added
CC||tatsuki_mak...@hotmail.com
--- Co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254763
--- Comment #18 from Mark Millard ---
(In reply to Matteo Riondato from comment #15)
Well, bug #223553 was specifically about /usr/bin/bsdgrep
(for how things were at the time). The environment has
progressed and the issues are certainly n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254763
--- Comment #19 from Mark Millard ---
(In reply to Tatsuki Makino from comment #17)
/usr/bin/time -l cat access_log.txt > output.log
would also mix reading (access_log.txt) and writing (output.log).
Does it produce odd timings? Or is the
15 matches
Mail list logo