Who would have though that dmesg didn't understand message buffers?

Fixed the following bugs:
- the buffer was reprinted endlessly when msg.bufx == 0 and (for a
different reason) when msg.bufx ==

Who would have though that dmesg didn't understand message buffers?

Fixed the following bugs:
- the buffer was reprinted endlessly when msg.bufx == 0 and (for a
different reason) when msg.bufx == 1.
- the last byte of the buffer wasn't printed except in the the infinite
loop cases.
- the comment about walking the buffer didn't match the (correct) code.
- minor -Wall and style bugs.
Not fixed:
- excessive newline processing which hid the non-printing of the last
byte of the buffer.

show more ...

Add #include <err.h>.

Add setlocale LC_CTYPE

BSD 4.4 Lite sbin Sources

Note: XNSrouted and routed NOT imported here, they shall be imported with
usr.sbin.

Avoid moving onto a new line while testing if there is a syslog priority
in the buffer. This isn't exactly the patch that Stephen submitted, but
is based on one of his suggestions.

PR: 93841
Submit

Avoid moving onto a new line while testing if there is a syslog priority
in the buffer. This isn't exactly the patch that Stephen submitted, but
is based on one of his suggestions.

PR: 93841
Submitted by: Stephen Montgomery-Smith <stephen@math.missouri.edu>
MFC after: 2 weeks

show more ...

WARNS=6 cleanup:

- signed/unsigned conform.
- Better initialization of nlist[]. I think we should have
something like NLIST_NULL instead of the current (ugly)
form...

Print a usage message if a non-option is specified.
MFC after: 3 weeks

Don't add integers to void pointers.

Remove advertising clause from University of California Regent's license,
per letter dated July 22, 1999.

Approved by: core, imp

Not too much point specifying -N but not specifying -M.

Further simplify the code for printing the message buffer:
- Ensure that the buffer ends with "\n\0" to avoid special cases
and allow the use of strtol().
- Use strvisx() on each complete line i

Further simplify the code for printing the message buffer:
- Ensure that the buffer ends with "\n\0" to avoid special cases
and allow the use of strtol().
- Use strvisx() on each complete line instead of character by
character.

Submitted by: bde
MFC after: 1 week

show more ...

Don't print the oldest line in the message buffer if the buffer is
full, since that line is almost always incomplete. Make the parsing
of <%d> lines more strict.

Also simplify the logic a little:
-

Don't print the oldest line in the message buffer if the buffer is
full, since that line is almost always incomplete. Make the parsing
of <%d> lines more strict.

Also simplify the logic a little:
- Start off by making the buffer linear so that we don't have to
deal with it wrapping around (suggested by bde).
- Process line by line rather than byte at a time.

show more ...

Replace the code for reading and writing the kernel message buffer
with a new implementation that has a mostly reentrant "addchar"
routine, supports multiple message buffers in the kernel, and hides

Replace the code for reading and writing the kernel message buffer
with a new implementation that has a mostly reentrant "addchar"
routine, supports multiple message buffers in the kernel, and hides
the implementation details from callers.

The new code uses a kind of sequence number to represend the current
read and write positions in the buffer. This approach (suggested
mainly by bde) permits the read and write pointers to be maintained
separately, which reduces the number of atomic operations that are
required. The "mostly reentrant" above refers to the way that while
it is now always safe to have any number of concurrent writers,
readers could see the message buffer after a writer has advanced
the pointers but before it has witten the new character.

Discussed on: freebsd-arch

show more ...

bufpos is used in size_t contexts, so make it one.

Include <nlist.h> for nlist interfaces instead of depending on namespace
pollution in <kvm.h>.

o Remove __P
o Use ANSI function definitions
o mark usage() as __dead2

add -a to usage()

Submitted by: Ashley Penney <ashp@unloved.org>
MFC after: 3 days

Use the kern.msgbuf sysctl to get the message buffer on a running
kernel, and remove setgid kmem, which is not needed any more.

Backout -a restriction hack.

Requested by: rwatson

Restrict -a to root only.

PR: bin/25337

Add a -a option to show the entire message buffer.

$Id$ -> $FreeBSD$

Use an error message that more clearly indites(sp?) an out-of-sync
kernel+userland when that is the case.

PR: bin/7414

Use .Pa for filenames. Use .Bl/.El in FILES section. Remove unused #includes.

Make the size of the msgbuf (dmesg) a "normal" option.