[Bug 160225] [periodic] /etc/periodic/weekly/310.locate doesn't see /etc/locate.rc.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160225 Wolfram Schneider changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|ed...@freebsd.org Blocks||124119 CC||wo...@freebsd.org Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=124119 [Bug 124119] locate(1) doesn't check /etc/locate.rc for the default database -- 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 201243] locate misses on too large paths
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201243 Wolfram Schneider changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|wo...@freebsd.org CC||wo...@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 211501] locate(1): Misleading help message
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211501 Wolfram Schneider changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|wo...@freebsd.org CC||wo...@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 126936] locate.updatedb(8): updatedb fails silently when attempting to search a disconnected samba share
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=126936 Wolfram Schneider changed: What|Removed |Added CC||wo...@freebsd.org Assignee|freebsd-bugs@FreeBSD.org|wo...@freebsd.org --- Comment #2 from Wolfram Schneider --- I don't think that it is the job of locate to complain about stale mount points. But if it fails, it should display a reason why. IMHO the locate database should contain only local files, and not any network mounted disks as NFS or samba. -- 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 223023] locate statistics cannot handle large databases
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223023 Bug ID: 223023 Summary: locate statistics cannot handle large databases Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: wo...@freebsd.org `locate -S' may display wrong results for the statistics on large databases. Fix: use a different type, e.g. uintmax_t -- 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 223023] locate statistics cannot handle large databases
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223023 Wolfram Schneider changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|wo...@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 222632] connect(2) not available in capability mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632
Jan Kokemüller changed:
What|Removed |Added
CC||jan.kokemuel...@gmail.com
--- Comment #13 from Jan Kokemüller ---
I've noticed that connectat(AT_FDCWD, ...) will even work on AF_INET sockets
created in capabilities mode. Surely this is not intended to work? Am I missing
something? bindat(AT_FDCWD, ...) also works.
if (cap_enter() < 0) {
err(1, "cap_enter");
}
int sock = socket(AF_INET, SOCK_STREAM, 0);
if (sock < 0) {
err(1, "socket");
}
struct sockaddr_in sin;
sin.sin_family = AF_INET;
sin.sin_port = htons(22);
sin.sin_addr.s_addr = htonl(0x7F01);
if (connectat(AT_FDCWD, sock, (struct sockaddr *)(&sin),
sizeof(struct sockaddr_in)) < 0) {
err(1, "connect");
}
--
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 223031] bsdgrep behaves incorrectly when given multiple patterns
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223031 Bug ID: 223031 Summary: bsdgrep behaves incorrectly when given multiple patterns Product: Base System Version: 10.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: j.deboynepollard-newsgro...@ntlworld.com See https://unix.stackexchange.com/questions/398223/ for how to replicate this. Some investigation reveals that this is apparently down to the pmatch object in the procline() function not being used properly. In the outer loop, it is being used to track the start and end position within the current input line. However, if multiple patterns are provided, in the inner loop it is overwritten by the first call to fastexec()/regexec() and not reinitialized with st and l->len for the next. The (re)initialization code for pmatch.rm_so and pmatch.rm_eo needs to be moved down into the inner loop, so that it is set correctly for every pattern, not just for the first one. This also means that the if (st == (size_t)pmatch.rm_so) code in the outer loop is probably wrong, too, as that will only detect the output of the last fastexec()/regexec() call for the last of multiple patterns. Perhaps there should be one pmatch object per pattern. -- 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 223031] bsdgrep behaves incorrectly when given multiple patterns
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223031 Conrad Meyer changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|kev...@freebsd.org CC||c...@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 143699] [patch] brandelf(1): extend brandelf's OS knowledge
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=143699 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #5 from Ed Maste --- The patch can go in and be merged into ELF Tool Chain's copy from 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 221772] vt(4) lacks (some?) semi-graphics, causing visible regression to the curses apps
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221772 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #2 from Ed Maste --- Can you attach reproduction instructions? -- 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 211922] Marked areas do not get cleared after they get scrolled out of the buffer on vt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211922 Ed Maste changed: What|Removed |Added Flags|mfc-stable10? |mfc-stable10+ -- 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 223036] nfsdumpstate client IP address broken for 64bit arches plus IPv6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223036 Bug ID: 223036 Summary: nfsdumpstate client IP address broken for 64bit arches plus IPv6 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: rmack...@freebsd.org Created attachment 187202 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187202&action=edit Fix nfsdumpstate client IP addr for IPv4 on 64bit and NFSv4.1 nfsdumpstate does not report the client IP address for the clientID. This can occur when: - The server is a 64bit architecture. This was caused by the code erroneously assuming that a "u_long" was a uint32_t and would exactly store an IPv4 host address. --> The attached patch fixes this. - The server didn't fill in the field for NFSv4.1 clients. --> The attached patch fixes this. - The client is using IPv6. This was not handled by the original NFSv4 code since the original RFC-3530 did not specify a way to define a IPv6 client callback address. --> I think that RFC-7530 addresses this and it needs to be fixed, but I don't have a patch yet. -- 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 223036] nfsdumpstate client IP address broken for 64bit arches plus IPv6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223036 Rick Macklem changed: What|Removed |Added Flags||mfc-stable10?, ||mfc-stable11? Assignee|freebsd-bugs@FreeBSD.org|rmack...@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"
