[Bug 18100] [patch] from(1): update to src/usr.bin/from/from.c for multiple mboxes

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=18100

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Feedback Timeout
 CC||go...@freebsd.org

--- Comment #3 from Oleksandr Tymoshenko  ---
Looks like due to GNATS/BZ converter's confusion of the suspended state PR
somehow got to "In Progress" state. Closing to match the history of transitions

-- 
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 214705] Kernel panic trying to playback encrypted DVD, "Fatal trap 12: page fault while in kernel mode"

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214705

--- Comment #9 from Joshua Kinard  ---
(In reply to Oleksandr Tymoshenko from comment #8)

All good.  The same laptop is on 12.0-RELEASE and hasn't had any problems w/
DVD playback in over a year.  Thanks!

-- 
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 41817] [patch] pw(8): pw groupshow doesn't include the login group

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=41817

Oleksandr Tymoshenko  changed:

   What|Removed |Added

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

--- Comment #6 from Oleksandr Tymoshenko  ---
Works as intended according to the Handbook

-- 
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 37844] [patch] [build] make knob to not install progs with suid/sgid set

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=37844

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 CC||go...@freebsd.org
 Status|Open|Closed

--- Comment #4 from Oleksandr Tymoshenko  ---
PR has been idle for some time. Closing as Overcome By Events since patch no
longer applies. Feel free to re-open if there is interest in implementing this
feature.

-- 
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 33809] [patch] mount_nfs(8) has trouble with embedded ':' in path

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=33809

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
 Resolution|--- |FIXED
 Status|Open|Closed

--- Comment #6 from Oleksandr Tymoshenko  ---
This was solved by base r203490:

Introduce '[ipaddr]:path' notation.
Since the existing implementation searches ':' backward, a path which
includes ':' could not be mounted.  You can now mount such path by
enclosing an IP address by '[]'.
Though we should change to search ':' forward, it will break
'ipv6addr:path' which is currently working.  So, it still searches ':'
backward, at least for now.

-- 
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 196239] [PATCH] drm2 and i915kms compiled into kernel on 9.3-STABLE

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196239

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 CC||go...@freebsd.org
 Status|New |Closed

--- Comment #3 from Oleksandr Tymoshenko  ---
FreeBSD 9 is no longer supported version.

-- 
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 144531] [patch] cp(1) show percentage complete

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144531

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Rejected
 CC||go...@freebsd.org

--- Comment #6 from Oleksandr Tymoshenko  ---
As Alexander mentioned - this feature is unlikely to be added to cp(1) unless
someone with commit bit would push it through review. Considering this I'm
closing it as "Rejected". If somebody wants to pick this PR up and work on it -
please feel free to reopen.

-- 
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 145082] [patch] w(1), uptime(1) to use 24H time by default

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=145082

Oleksandr Tymoshenko  changed:

   What|Removed |Added

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

--- Comment #5 from Oleksandr Tymoshenko  ---
The time format is locale-specific:

% env LANG=uk_UA.UTF-8 w
19:16  up 18 days,  1:24, 9 users, load averages: 0,00 0,00 0,00

% env LANG=en_US.ISO8859-1 w
 7:18PM  up 18 days,  1:26, 9 users, load averages: 0.02, 0.01, 0.00

There is no need to change default behavior.

-- 
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 146592] [libpcap] [patch] libpcap 1.0.0 doesn't have error message for nonexistent interface

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=146592

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events
 CC||go...@freebsd.org

--- Comment #2 from Oleksandr Tymoshenko  ---
Not reproducible in 13-CURRENT:

% sudo tcpdump -i something
tcpdump: something: No such device exists
(BIOCSETIF failed: Device not configured)

-- 
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 80775] [kernel] [patch] sysctl_handle_string should have a timeout

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=80775

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events
 CC||go...@freebsd.org

--- Comment #3 from Oleksandr Tymoshenko  ---
sysctl_handle_string no longer has retry loop, closing as OBE

-- 
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 65803] [patch] ps(1) enhancements (posix syntax, and more)

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=65803

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||go...@freebsd.org
 Resolution|--- |Overcome By Events

--- Comment #114 from Oleksandr Tymoshenko  ---
ps and kernel source code progressed since 2004 and patches no longer apply
cleanly.

-- 
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 59220] [patch] systat(1) device select (:only) broken

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=59220

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
 Resolution|--- |FIXED
 Status|Open|Closed

--- Comment #5 from Oleksandr Tymoshenko  ---
Closing as fixed, I'll handle MFC separately. Thanks for submitting and sorry
it hasn't been handled sooner.

-- 
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 59220] [patch] systat(1) device select (:only) broken

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=59220

--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:

Author: gonzo
Date: Wed Jan 23 02:46:36 UTC 2019
New revision: 343338
URL: https://svnweb.freebsd.org/changeset/base/343338

Log:
  Fix systat's :only command parser for the multiple arguments case

  According to systat(1) :only option is supposed to accept multiple drives
  but the parser for its arguments stops after first entry. Fix the parser
  logic to accept multiple drives.

  PR:   59220
  Reported by:  Andy Farkas 
  MFC after:1 week

Changes:
  head/usr.bin/systat/devs.c

-- 
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 233343] [libedit] bind command reads out of bounds

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233343

--- Comment #14 from Yuichiro NAITO  ---
(In reply to Jilles Tjoelker from comment #12)
Thanks for the comment.
My understanding was a little wrong.
I saw `bind` messages were always output to STDERR.
So my patch can be reduced to just swap el's stderr and stdout temporarily.
I updated 'sh.patch'.

It seems ad hoc way, but I have no idea about better than this.

-- 
You are receiving this mail because:
You are on the CC list 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 233343] [libedit] bind command reads out of bounds

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233343

Yuichiro NAITO  changed:

   What|Removed |Added

 Attachment #200905|0   |1
is obsolete||

--- Comment #13 from Yuichiro NAITO  ---
Created attachment 201348
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201348=edit
sh.patch

-- 
You are receiving this mail because:
You are on the CC list 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 28236] [patch] iso-8859-1_to_cp437.scm doesn't contain some useful mappings

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=28236

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Resolution|--- |Not Enough Information
 CC||go...@freebsd.org
 Status|Open|Closed

--- Comment #3 from Oleksandr Tymoshenko  ---
Closing as "Not Enough Information" since no patch against sources was
provided. Feel free to re-open this PR if the issue is still reproducible in
recent versions of FreeBSD.

Thanks

-- 
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 235107] 'make buildworld' of 12.0-RELEASE sources fails, pf.h not found

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235107

--- Comment #5 from Kristof Provost  ---
Have you previously done buildworld/installworld with these or other flags? 

I can't seem to reproduce this, and I see no obvious reason why it'd happen.
You're not disabling pf, so the header should be installed. And I've tested
WITHOUT_PF, and that builds fine for me too.

-- 
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 19535] [procfs] [patch] procfs_rlimit tidyup

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=19535

--- Comment #8 from Adrian Chadd  ---
holy crap i wonder if this is still a problem!

-- 
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 19535] [procfs] [patch] procfs_rlimit tidyup

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=19535

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org

--- Comment #7 from Oleksandr Tymoshenko  ---
Adrian, do you have any plans committing this or can the PR be 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 231828] em(4) is unusable after suspend/resume

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231828

--- Comment #8 from Kurt Jaeger  ---
rgrimes mentioned that some work is in progress to have an errata+fix
for this and other network-related fixes.

-- 
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 185742] [hyper-v] r260387 breaks Hyper-V (Win 2012r2 Server) [regression]

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185742

Oleksandr Tymoshenko  changed:

   What|Removed |Added

   Assignee|sco...@freebsd.org  |b...@freebsd.org
 CC||go...@freebsd.org
 Status|Open|Closed
 Resolution|--- |Feedback Timeout

--- Comment #4 from Oleksandr Tymoshenko  ---
Closing as "Feedback timeout" and returning to the pool. Feel free to reopen
the issue if it is still reproducible with recent versions of FreeBSD.

-- 
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 119205] [dc] [patch] Collect various stats regarding dc(4) interrupts

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=119205

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org

--- Comment #11 from Oleksandr Tymoshenko  ---
Peter, is this patch still relevant, are you going to implement John's
suggestion of per-device stats sysctls?

-- 
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 30052] [dc] [patch] dc driver queues outgoing pkts indefinitely if no link

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=30052

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
 Resolution|--- |Overcome By Events
 Status|Open|Closed

--- Comment #8 from Oleksandr Tymoshenko  ---
The code in question has been changed and patch no longer applies. Closing as
OBE. Feel free to reopen if issues is reproducible on recent FreeBSD versions.

-- 
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 30321] [patch] strftime(3) '%s' format does not work properly

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=30321

David Bright  changed:

   What|Removed |Added

 Resolution|--- |Unable to Reproduce
 Status|Open|Closed

--- Comment #6 from David Bright  ---
Works for me, at least in 12.0-RELEASE

-- 
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 41271] [patch] non-suid crontab(1)

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=41271

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||go...@freebsd.org
 Resolution|--- |Overcome By Events

--- Comment #4 from Oleksandr Tymoshenko  ---
This bug has been idle for a long time. Closing as OBE but feel free to re-open
it if the issue is still valid.

-- 
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 36911] [ata] ATA cannot be disabled with hints or through BIOS

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=36911

Oleksandr Tymoshenko  changed:

   What|Removed |Added

 CC||go...@freebsd.org
 Resolution|--- |Works As Intended
 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 235136] cron email header has bogus date value

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235136

Bug ID: 235136
   Summary: cron email header has bogus date value
   Product: Base System
   Version: 11.2-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: ml-freebsd@vintners.net

Obscure problem with 'cron'.

I have a script that fires hourly, normally producing no output, thus no email.
 It has started reporting a problem (nothing to do with FreeBSD), thus is now
emailing me output hourly.

The problem is that the email coming through my 'spamassassin' filter, is
getting flagged as 'DATE_IN_FUTURE'_*.  (This forces it into the "probably
spam" range.)  As time goes by, this will go up from '_06_12' to '_12_24', etc.

Looking at the Recieved: headers, it appears that the email arrives from
'localhost' with a time setting that does not change, regardless of the time
the 'cron' job fired.

And, in fact, the time appears to be pretty close to the boot time of the
system.

My guess is that when 'cron' builds the header of the email, for the "Date:"
it's using the start time of the 'cron' daemon, instead of properly using the
time of this 'cron' job.  I guess I would expect it should be using the time
_now_, as opposed to the time the job was started, but I'll let you figure that
out.

-- 
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 231828] em(4) is unusable after suspend/resume

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231828

--- Comment #7 from Chris  ---
I have applied the patch from PR#224059 and suspended my machine at least 8
times today without any issues. Thanks!

Do we know if 12.0 will be updated, or will I need to keep applying the patch
until 12.1 is released?

-- 
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 235132] bectl destroy … cannot destroy …: dataset already exists

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235132

Bug ID: 235132
   Summary: bectl destroy … cannot destroy …: dataset already
exists
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: grahamper...@gmail.com



Below: is it normal for simple destruction, without specifying a snapshot, to
behave in this way? (Given the 'unknown error, I imagine that it's not normal.)

If it helps: I do not recall creating a snapshot.

TIA



root@momh167-gjp4-8570p:~ # bectl list
BE Active Mountpoint Space Created
r343023NR /  34.3G 2019-01-14 17:49
r342851-  -  1.72M 2019-01-07 19:31
r342851-with-locks -  -  8.93G 2019-01-22 01:34
r342466-  -  34.7M 2019-01-07 07:53
default-  -  2.16M 2018-12-22 05:01
root@momh167-gjp4-8570p:~ # bectl destroy r342851-with-locks
cannot destroy 'copperbowl/ROOT/r342851-with-locks@2019-01-22-01:34:50':
dataset already exists
unknown error
root@momh167-gjp4-8570p:~ # date ; uname -v
Tue Jan 22 16:30:47 GMT 2019
FreeBSD 13.0-CURRENT r343023 GENERIC-NODEBUG 
root@momh167-gjp4-8570p:~ # bectl list -s
BE/Dataset/SnapshotActive Mountpoint
Space Created

r343023
  copperbowl/ROOT/r343023  NR / 
34.3G 2019-01-14 17:49
  r343023@2019-01-07   -  - 
1.08M 2019-01-07 07:48
  r343023@2019-01-07-07:53:37  -  - 
1.07M 2019-01-07 07:53
  r343023@2019-01-07-19:31:37  -  - 
33.6M 2019-01-07 19:31
  r343023@2019-01-14-17:49:17  -  - 
5.56G 2019-01-14 17:49

r342851
  copperbowl/ROOT/r342851  -  - 
728K  2019-01-07 19:31
copperbowl/ROOT/r342851-with-locks@2019-01-22-01:34:50 -  - 
1.01M 2019-01-22 01:34

r342851-with-locks
  copperbowl/ROOT/r342851-with-locks   -  - 
3.36G 2019-01-22 01:34
copperbowl/ROOT/r343023@2019-01-14-17:49:17-  - 
5.56G 2019-01-14 17:49
  r342851-with-locks@2019-01-22-01:34:50   -  - 
1.01M 2019-01-22 01:34

r342466
  copperbowl/ROOT/r342466  -  - 
1.13M 2019-01-07 07:53
copperbowl/ROOT/r343023@2019-01-07-19:31:37-  - 
33.6M 2019-01-07 19:31

default
  copperbowl/ROOT/default  -  - 
1.09M 2018-12-22 05:01
copperbowl/ROOT/r343023@2019-01-07-07:53:37-  - 
1.07M 2019-01-07 07:53
root@momh167-gjp4-8570p:~ #

-- 
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 235108] GELI leaves streaks of zeros for every encrypted sector; suggestion to randomize

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235108

--- Comment #4 from Arjan van der Velde  ---
(In reply to Conrad Meyer from comment #3)

ok. well, regardless of opinions on what generally would actually happen when
asked for a password by law enforcement, i think there is a case for making it
harder to detect the presence of a geli provider so, i figured i put the idea
out there.

-- Arjan

-- 
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 235125] Process was killed: out of swap space on gmirror + zfs

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235125

Bug ID: 235125
   Summary: Process was killed: out of swap space on gmirror + zfs
   Product: Base System
   Version: 11.2-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: alaa.alassa...@card-1.com

Hello,

We've got FreeBSD 11.2p8 installed on 2 SSDs which are mirrored using gmirror.
we also have a zpool which consists of 3x7 raidz1 drives, 2x Cache and 2x SLOG
and 1x spare.
dual Xeon CPUs and 128GB of Ram.

The first time this Problem accrued right after the 11.2p8 upgrade from p4:


Jan 14 17:04:22 san2 zfsd: POLLHUP detected on devd socket.
Jan 14 17:04:22 san2 kernel: pid 606 (devd), uid 0, was killed: out of swap
space
Jan 14 17:04:22 san2 kernel: Jan 14 17:04:22 san2 kernel: pid 606 (devd), uid
0, was killed: out of swap space
Jan 14 17:04:22 san2 zfsd: Disconnecting from devd.
Jan 14 17:04:22 san2 zfsd: ConnectToDevd: Connecting to devd.


we had to restart the machine. After 3 days we had the same Problem, but this
time multiple processes were killed:

--
Jan 19 10:49:49 san2 kernel: pid 610 (devd), uid 0, was killed: out of swap
space
Jan 19 10:49:49 san2 kernel: Jan 19 10:49:49 san2 kernel: pid 610 (devd), uid
0, was killed: out of swap space
Jan 19 11:09:49 san2 kernel: pid 835 (zabbix_agentd), uid 122, was killed: out
of swap space
Jan 19 11:09:49 san2 kernel: Jan 19 11:09:49 san2 kernel: pid 835
(zabbix_agentd), uid 122, was killed: out of swap space
Jan 19 11:10:48 san2 kernel: pid 847 (bareos-fd), uid 0, was killed: out of
swap space
Jan 19 11:10:48 san2 kernel: Jan 19 11:10:48 san2 kernel: pid 847 (bareos-fd),
uid 0, was killed: out of swap space
Jan 19 11:11:15 san2 kernel: pid 838 (ntpd), uid 233, was killed: out of swap
space
Jan 19 11:11:15 san2 kernel: Jan 19 11:11:15 san2 kernel: pid 838 (ntpd), uid
233, was killed: out of swap space
Jan 19 11:11:29 san2 kernel: pid 802 (ctld), uid 0, was killed: out of swap
space
Jan 19 11:11:29 san2 kernel: Jan 19 11:11:29 san2 kernel: pid 802 (ctld), uid
0, was killed: out of swap space
Jan 19 11:11:45 san2 kernel: pid 116 (adjkerntz), uid 0, was killed: out of
swap space
Jan 19 11:11:45 san2 kernel: Jan 19 11:11:45 san2 kernel: pid 116 (adjkerntz),
uid 0, was killed: out of swap space
Jan 19 11:12:15 san2 kernel: pid 971 (getty), uid 0, was killed: out of swap
space
Jan 19 11:12:15 san2 kernel: Jan 19 11:12:15 san2 kernel: pid 971 (getty), uid
0, was killed: out of swap space
Jan 19 11:12:29 san2 kernel: pid 32950 (getty), uid 0, was killed: out of swap
space
Jan 19 11:12:29 san2 kernel: Jan 19 11:12:29 san2 kernel: pid 32950 (getty),
uid 0, was killed: out of swap space
Jan 19 11:12:46 san2 kernel: pid 32951 (getty), uid 0, was killed: out of swap 
-

Messages kept on repeating until we restarted the machine.
We tried disabling zfsd, but that didn't help.

This Machine is in production its really frustrating to have this behavior. I
will gladly provide any more info/tests when needed.

Thank you


Here is some more info:
--

root@san2:~ # gmirror status
   NameStatus  Components
mirror/boot  COMPLETE  gpt/boot0 (ACTIVE)
   gpt/boot1 (ACTIVE)
mirror/swap  COMPLETE  gpt/swap0 (ACTIVE)
   gpt/swap1 (ACTIVE)
mirror/root  COMPLETE  gpt/root0 (ACTIVE)
   gpt/root1 (ACTIVE)

zpool list
NAME   SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUP  HEALTH 
ALTROOT
san2pool  37.9T  17.4T  20.4T- - 2%46%  1.00x  ONLINE 
-


root@san2:~ # vmstat
procs  memory   pagedisks faults cpu
r b w  avm   fre   flt  re  pi  pofr   sr ad0 ad1   insycs us sy id
0 0 2 409M  3.2G  1170   1   5   4  1569 1355   0   0 3837   800  9140  0  7 93


Device  1K-blocks UsedAvail Capacity
/dev/mirror/swap   838860426528  8362076 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 234969] ctladm: assertion fails in function nvlist_destroy

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234969

Mark Linimon  changed:

   What|Removed |Added

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

--- Comment #2 from Mark Linimon  ---
Fixed by r342467.

-- 
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 234969] ctladm: assertion fails in function nvlist_destroy

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234969

--- Comment #1 from kukub...@go2.pl ---
https://github.com/freebsd/freebsd/commit/931e1ea4131323e8cbee7ac56819fc00af90c038
solves the issue.

-- 
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 235122] rc.subr limits call breaks non-root usage

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235122

Kubilay Kocak  changed:

   What|Removed |Added

 Status|New |Open
   Severity|Affects Only Me |Affects Some People
   Keywords||easy, feature, needs-qa,
   ||regression
   Assignee|b...@freebsd.org|r...@freebsd.org

--- Comment #1 from Kubilay Kocak  ---
Thank you for the report and patch Markus. Could you please include your patch
as an attachment?

-- 
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 235122] rc.subr limits call breaks non-root usage

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235122

Bug ID: 235122
   Summary: rc.subr limits call breaks non-root usage
   Product: Base System
   Version: 11.2-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: conf
  Assignee: b...@freebsd.org
  Reporter: freebsd-b...@virtualtec.ch

We sometimes want customers to be able to restart services (like ldap) 
running on non-standard and non-privileged ports. With the new unconditional 
call to "limits" in the rc.subr start function, this fails:

$ sh /usr/local/etc/rc.d/slapd start
Starting slapd.
limits: setrlimit datasize: Operation not permitted

I suggest a change like the following:

--- /etc/rc.subr.orig   2019-01-22 10:40:13.973245000 +0100
+++ /etc/rc.subr2019-01-22 09:51:18.058288000 +0100
@@ -1073,7 +1073,9 @@
fi

# Prepend default limits
-   _doit="$_cd limits -C $_login_class $_doit"
+   if [ `/usr/bin/id -u` -eq 0 ]; then
+   _doit="$_cd limits -C $_login_class $_doit"
+   fi

# run the full command
#

and the same service can now be maintained by a non privileged user:

$ sh /usr/local/etc/rc.d/slapd start
Starting slapd.

Kind regards,
Markus

-- 
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 235107] 'make buildworld' of 12.0-RELEASE sources fails, pf.h not found

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235107

--- Comment #4 from o...@oz42.eu ---
Yes, it is a 12.0-RELEASE system.

This is the src.conf:

WITHOUT_ACCT=YES
WITHOUT_AMD=YES
WITHOUT_ASSERT_DEBUG=YES
WITHOUT_ATM=YES
#
WITHOUT_AUTHPF=YES
WITHOUT_BHYVE=YES
WITHOUT_BLUETOOTH=YES
WITHOUT_BOOTPARAMD=YES
WITHOUT_BOOTPD=YES
WITHOUT_BSNMP=YES
WITHOUT_CALENDAR=YES
WITHOUT_CAPSICUM=YES# includes WITHOUT_CASPER
WITHOUT_CCD=YES
WITHOUT_CDDL=YES# includes WITHOUT_CTF WITHOUT_ZFS
#
WITHOUT_LLVM_TARGET_AARCH64=YES
WITHOUT_LLVM_TARGET_ALL=YES
WITHOUT_LLVM_TARGET_ARM=YES
WITHOUT_LLVM_TARGET_MIPS=YES
WITHOUT_LLVM_TARGET_POWERPC=YES
WITHOUT_LLVM_TARGET_SPARC=YES
#
WITHOUT_CTM=YES
WITHOUT_CUSE=YES
WITHOUT_CXGBETOOL=YES
WITHOUT_DEBUG_FILES=YES
WITHOUT_DICT=YES
WITHOUT_DMAGENT=YES
WITHOUT_EXAMPLES=YES
WITHOUT_FLOPPY=YES
WITHOUT_FTP=YES
WITHOUT_GCOV=YES
WITHOUT_GSSAPI=YES
WITHOUT_HAST=YES
WITHOUT_HTML=YES
WITHOUT_HYPERV=YES
WITHOUT_INET6=YES
WITHOUT_INETD=YES
WITHOUT_IPFILTER=YES
# WITHOUT_IPFW=YES
WITHOUT_IPSEC_SUPPORT=YES
WITHOUT_ISCSI=YES
WITHOUT_JAIL=YES
WITHOUT_KDUMP=YES
WITHOUT_KERBEROS=YES
WITHOUT_KERNEL_SYMBOLS=YES
WITHOUT_LEGACY_CONSOLE=YES
WITHOUT_LPR=YES
WITHOUT_LS_COLORS=YES
WITHOUT_MAILWRAPPER=YES
WITHOUT_MLX5TOOL=YES
WITHOUT_MODULE_DRM=YES
WITHOUT_MODULE_DRM2=YES
WITHOUT_NDIS=YES
WITHOUT_NIS=YES
WITHOUT_PMC=YES
WITHOUT_PPP=YES
WITHOUT_PROFILE=YES
WITHOUT_RADIUS_SUPPORT=YES
WITHOUT_RBOOTD=YES
WITHOUT_ROUTED=YES
WITHOUT_SENDMAIL=YES
WITHOUT_SOURCELESS=YES  # no sourceless code in kernel, includes
WITHOUT_SOURCELESS_HOST WITHOUT_SOURCELESS_UCODE
WITHOUT_TCP_WRAPPERS=YES
WITHOUT_TESTS=YES   # includes WITHOUT_DTRACE_TESTS WITHOUT_TESTS_SUPPORT
WITHOUT_TFTP=YES
WITHOUT_TIMED=YES
WITHOUT_USB=YES
WITHOUT_USB_GADGET_EXAMPLES=YES
WITHOUT_WIRELESS=YES# includes WITHOUT_WIRELESS_SUPPORT=YES
WITHOUT_WPA_SUPPLICANT_EAPOL=YES
WITHOUT_ZFS=YES

-- 
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 235107] 'make buildworld' of 12.0-RELEASE sources fails, pf.h not found

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235107

--- Comment #3 from Kristof Provost  ---
Are you building on 12.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 235107] 'make buildworld' of 12.0-RELEASE sources fails, pf.h not found

2019-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235107

--- Comment #2 from o...@oz42.eu ---
It was a simple 'make buildworld'

-- 
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"