[Bug 194864] New: newsyslog(8) does not delete old files after config change
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194864
Bug ID: 194864
Summary: newsyslog(8) does not delete old files after config
change
Product: Base System
Version: 10.0-STABLE
Hardware: amd64
OS: Any
Status: Needs Triage
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: freebsd-bugs@FreeBSD.org
Reporter: r...@bytecamp.net
Lets assume the following entry in /etc/newsyslog.conf:
/var/log/httpd-suexec.log 640 14*@T00 JC
After 14 days, there are 14 compressed files httpd-suexec.N.log.bz2 in
/var/log.
Now lower the count from 14 to 7:
/var/log/httpd-suexec.log 640 7*@T00 JC
One may assume, that newsyslog will delete 7 files in the next run, since there
should only be kept 7 old logfiles.
But it doesn't, it just deletes the 8th old logfile (httpd-suexec.log.7.bz2)
and keeps httpd-suexec.log.{8,9,10,11,12,13}.bz2.
--
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 184597] [PATCH] Fix rfcomm_sppd(1) pseudo slave TTY mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184597 --- Comment #5 from commit-h...@freebsd.org --- A commit references this bug: Author: emax Date: Thu Nov 6 16:32:01 UTC 2014 New revision: 274182 URL: https://svnweb.freebsd.org/changeset/base/274182 Log: MFC r273548 Change the code to use the openpty(3) API which uses the pts(4) driver instead of the pty(4) driver. PR:184597 Submitted by:tobias.rehbein Changes: _U stable/10/ stable/10/usr.bin/bluetooth/rfcomm_sppd/Makefile stable/10/usr.bin/bluetooth/rfcomm_sppd/rfcomm_sppd.1 stable/10/usr.bin/bluetooth/rfcomm_sppd/rfcomm_sppd.c -- 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 194729] 11-CURRENT cannot be built on 10-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194729 Bug 194729 depends on bug 194361, which changed state. Bug 194361 Summary: [BUG] 11-CURRENT does not build on 10.1-STABLE https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194361 What|Removed |Added Status|Needs Triage|Issue Resolved Resolution|--- |Not A Bug -- 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 194361] [BUG] 11-CURRENT does not build on 10.1-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194361 ne...@nevermind.kiev.ua changed: What|Removed |Added Status|Needs Triage|Issue Resolved Resolution|--- |Not A Bug -- 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 194729] 11-CURRENT cannot be built on 10-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194729 ne...@nevermind.kiev.ua changed: What|Removed |Added Status|Needs Triage|Issue Resolved Resolution|--- |Not A Bug -- 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 194664] [vt] radeonkms_load="YES" in loader.conf.local halts system, "Failed to load firmware!"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194664 --- Comment #3 from crum.z...@gmail.com --- still no luck. I noted /boot/modules only had virtualbox kernel modules in it, so I copied the entire /boot/kernel directory into it. Still had the same result. #vesa_load="YES" hw.pci.default_vgapci_unit="0" autoboot_delay="5" loader_logo="beastie" module_path="/boot/modules" kern.vty=vt #radeonkms_load="YES" #radeonkmsfw_CAYMAN_pfp_load="YES" I can still kldload the radeonkms driver after signing in. -- 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 194664] [vt] radeonkms_load="YES" in loader.conf.local halts system, "Failed to load firmware!"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194664 --- Comment #4 from Tijl Coosemans --- (In reply to crum.zach from comment #3) > still no luck. I noted /boot/modules only had virtualbox kernel modules in > it, so I copied the entire /boot/kernel directory into it. Still had the > same result. That should not be necessary. > #vesa_load="YES" > hw.pci.default_vgapci_unit="0" > autoboot_delay="5" > loader_logo="beastie" > module_path="/boot/modules" > kern.vty=vt > #radeonkms_load="YES" > #radeonkmsfw_CAYMAN_pfp_load="YES" There are more CAYMAN firmware modules. Maybe you need to load all of them: radeonkms_load="YES" radeonkmsfw_CAYMAN_mc_load="YES" radeonkmsfw_CAYMAN_me_load="YES" radeonkmsfw_CAYMAN_pfp_load="YES" radeonkmsfw_CAYMAN_rlc_load="YES" -- 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 194752] libusb-0.1.pc should be libusb.pc for compatibility
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194752 Tijl Coosemans changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org -- 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 194872] New: [netmap] documentation for bridge/pkt-gen doesn't mention the updated interface format (netmap:X, vale:X) nor how to configure a specific ring
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194872 Bug ID: 194872 Summary: [netmap] documentation for bridge/pkt-gen doesn't mention the updated interface format (netmap:X, vale:X) nor how to configure a specific ring Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: adr...@freebsd.org Hi, The netmap documentation for pkt-gen and bridge don't include the updated interface requirements. The netmap man page gives an example interface as 'ix0' which doesn't work. It needs to be 'netmap:ix0' . It also doesn't make clear that the way to specify a specific ring here is 'netmap:ix0-ringid'. I think we'd make things a lot easier to get started if the documentation for the netmap interface strings was updated in both the netmap documentation and the example tools. Thanks! -adrian -- 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 194872] [netmap] documentation for bridge/pkt-gen doesn't mention the updated interface format (netmap:X, vale:X) nor how to configure a specific ring
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194872 Adrian Chadd changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org -- 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 194204] getentropy(2): sys call from openbsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194204 --- Comment #5 from Mateusz Guzik --- I'm no crypto expert. Turns out FreeBSD's arc4rand uses RC4, while OpenBSD's version uses something based on ChaCha which is stronger than RC4. I don't think we should provide a syscall with weaker randomness than one provided with original implementation. -- 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 194204] getentropy(2): sys call from openbsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194204 --- Comment #6 from David CARLIER --- I did as well an updated related to arc4random RC4 => Chacha 20 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182610 -- 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 190669] 'emmintrin.h' file not found - in /usr/src/lib/clang/libclangbasic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190669 C Hutchinson changed: What|Removed |Added CC||portmas...@bsdforge.com --- Comment #19 from C Hutchinson --- I find myself struggling with what looks like the same issue on a recent 11-CURRENT install (11-CURRENT #1 amd64 r274134 Nov 5 12:56:14 PST 2014) svn info /usr/ports Revision: 372176 As you can see, I've built and installed kernel/world. I did, perform a make delete-old, following the install world. Which removed the clang that was delivered from the base install on the bootonly iso. However, I have installed lang/gcc-48, which does have xmmintrin.h in it's include tree. It is also my understanding that clang isn't mandatory. But I seem to have no end of problems with ports looking for, and subsequently not finding xmmintrin.h. Even though it's an included header with lang/gcc-48. Where lies the problem? I should also probably note; I haven't [intentionally] enabled, or used ccache. Thank you for all your time, and consideration. --Chris -- 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"
