| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
too long for the column they're printed in.
Move variable definitions out of netstat.h and into main.c.
Clean up some warnings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A route generated from an RTF_CLONING route had the RTF_WASCLONED flag
set but did not have a reference to the parent route, as documented in
the rtentry(9) manpage. This prevented such routes from being deleted
when their parent route is deleted.
Now, for example, if you delete an IP address from a network interface,
all ARP entries that were cloned from this interface route are flushed.
This also has an impact on netstat(1) output. Previously, dynamically
created ARP cache entries (RTF_STATIC flag is unset) were displayed as
part of the routing table display (-r). Now, they are only printed if
the -a option is given.
netinet/in.c, netinet/in_rmx.c:
When address is removed from an interface, also delete all routes that
point to this interface and address. Previously, for example, if you
changed the address on an interface, outgoing IP datagrams might still
use the old address. The only solution was to delete and re-add some
routes. (The problem is easily observed with the route(8) command.)
Note, that if the socket was already bound to the local address before
this address is removed, new datagrams generated from this socket will
still be sent from the old address.
PR: kern/20785, kern/21914
Reviewed by: wollman (the idea)
|
|
|
|
|
|
| |
remove the concept of a 'maintainer' of our make. there really isn't a
need for any one committer to hold an exclusive lock or serve as a filter
for this code.
|
|
|
|
|
|
|
|
|
|
| |
src/sys/modules/if_ef and possibly other things. I tested the build with
a make based on rev. 1.26, and it worked fine. Since I'm not particularly
inclined to figure out what's going on with this, it's probably prudent
just to back it out for now.
Found by: jkh
Suggested by: jhay
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
.endif statements but can't be placed in .elif. Basically, the problem
was that ParseSkipLine() didn't handle comments the same way that
ParseReadLine() did, and thus you had errors with comments that are on a
conditional line (i.e. "^.") rather than a non-conditional line.
MFC candidate for 4.3-STABLE and 3.5-STABLE.
PR: 25627
Bug found by: jhs
Fix submitted by: Seth Kingsley <sethk@osd.bsdi.com> (thanks!!)
|
|
|
|
|
|
| |
Don't roll our own version of trimdomain(), use the one in libutil.
Not objected to by: freebsd-audit
|
| |
|
|
|
|
|
|
|
|
| |
characters. This should avoid unattractive wrapping for people who are
stuck in an 80x24 screen. :-)
PR: 22270
Submitted by: William Carrel <williamc@go2net.com>
|
|
|
|
|
|
|
| |
root permission is not needed and the kerberos library is paranoid
about access control to the ticket file
PR: bin/20779
|
| |
|
|
|
|
| |
and remove leading `r'(aw) from it.
|
|
|
|
|
|
|
|
|
|
|
|
| |
list was cleared.
Rules with null suffixes would not be rebuilt when the suffixes were
added again.
Adding null suffix rules would fail when a rule for the same source was
declared before the suffix list was cleared.
PR: 23328, 24102
Reviewed by: will
Approved by: rwatson
|
|
|
|
|
|
|
|
| |
to the summary shown at the end of the transfer.
Some days, I really hate Unix...
Suggested by: cracauer
|
| |
|
|
|
|
|
| |
symbols. This allows lorder to be used more easily in a cross-build
environment.
|
| |
|
|
|
|
|
| |
PR: 25541
Submitted by: Nickolay Dudorov <nnd@mail.nsk.ru>
|
|
|
|
|
|
| |
(random() or arc4random())
Reviewed by: bde
|
|
|
|
| |
values that aren't updated for a particular network-layer address.
|
|
|
|
| |
while I'm here, fix bitrotted debug code generating template.
|
| |
|
|
|
|
| |
locales, so leads to confusion
|
| |
|
| |
|
|
|
|
|
|
|
| |
Don't treat pointer as a boolean, but instead test it against NULL.
Add warning for groups that don't exist
Submitted by: ru
|
|
|
|
|
|
|
|
| |
have a sane default.
Also add $FreeBSD$ while I'm here.
Pointed out by: bde
|
|
|
|
|
|
|
| |
Correct array sizes to reflect this.
Correct NUL termination after strncpy.
# Didn't to strncpy -> strlcpy change.
|
| |
|
|
|
|
|
| |
Also, snprinf is guaranteed by the new ansi standard to NUL terminate the
string, so we don't need to do that ourselves.
|
| |
|
|
|
|
|
| |
In addition, since we pass readlink MAXPATHLEN - 1, we would have never have
used that extra byte anyway.
|
|
|
|
| |
to it for the size of path.
|
|
|
|
| |
for ages.
|
|
|
|
|
|
|
| |
a given group.
o Minor code style cleanups while I'm here
Reviewed by: bde, kris, markm, audit@
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
prefix recusrion bug. Remove units which can be derived using prefixes
and other units.
Add new prefixes for 2^10, 2^20, etc...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Fix a bug where the recursion on prefixes where if recusrion failed
then the next attempt started too far along the string.
2) Up some internal limits that we were about to hit off.
3) Change the constness and signedness of some things and complete missing
prototypes.
4) Remove the readerror function 'cos it could print out the wrong
wrong file name. Replace it with more useful error messages.
5) Use sizeof when passing buffers to fgets.
6) Warn about empty prefix definitions.
Reviewed by: iedowse
|
| |
|
|
|
|
|
|
| |
waiting for a '}' nesting terminator)
Obtained from: OpenBSD rev 1.8
|
|
|
|
|
|
|
|
|
|
| |
fscale is a (64-bit) long. So just use a struct loadavg.
This fixes the recent failure of top on alphas:
top: sysctl(vm.loadavg...) failed: Cannot allocate memory
- use size_t for sizeof() so as to fix a few int/long warnings on alpha
Reviewed by: Thomas Moestl <tmoestl@gmx.net>
|
| |
|
| |
|
|
|
|
| |
install top with setgid bit.
|
|
|
|
|
|
|
|
| |
available via sysctl(). As a result, top should now be able to run without
setgid kmem.
Submitted by: Thomas Moestl <tmoestl@gmx.net>
Reviewed by: freebsd-audit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-E Interpret regular expressions followed by -regex and -iregex op-
tions as extended (modern) regular expressions rather than basic
regular expressions (BRE's). The re_format(7) manual page fully
describes both formats.
-iname pattern
Like -name, but the match is case insensitive.
-ipath pattern
Like -path, but the match is case insensitive.
-regex pattern
True if the whole path of the file matches pattern using regular
expression. To match a file named ``./foo/xyzzy'', you can use
the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but not
``xyzzy'' or ``/foo/''.
-iregex pattern
Like -regex, but the match is case insensitive.
These are meant to be compatible with other find(1) implementations
such as GNU's or NetBSD's except regexp library differences.
Reviewed by: sobomax, dcs, and some other people on -current
|
|
|
|
|
|
|
| |
Submitted by: Maxim Konovalov <maxim@macomnet.ru>
Silence a warning by renaming the 'pgtok' #define to 'vmstat_pgtok' so
as not to conflict with the 'pgtok' #define in sys/param.h
|
| |
|