| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Checking if it is > 0 doesn't make sense, because snprintf returns
how much space is needed if the buffer is too small. Instead, check
if the return value was greater than the buffer size, and truncate
the message if it was too long.
It isn't clear if snprintf can return a negative value in the case
of an error - I don't believe it can. If it can, then testing
v->iov_len won't help 'cos it is a size_t, not an ssize_t.
Also, as clang points out, we must always increment v here, because
later code depends on the message being in iov[5].
|
|
|
|
| |
WARNS?=3 until that's resolved.
|
|
|
|
|
|
|
|
| |
WARNS=6 setting in HEAD (unlike stable/8), so it's best
to remove the line entirely.
Pointed out by: jh
Approved by: des (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
standard ports, but it can't *receive* them (port 514 is
hardcoded). This commit adds that missing feature.
(NB: I actually needed this feature for a server farm where
multiple jails run with shared IP addresses, and every jail
should have its own syslogd process.)
As a side effect, syslogd now compiles with WARNS=6.
Approved by: des (mentor)
MFC after: 3 weeks
|
| |
|
|
|
|
|
| |
Because strings are guaranteed to be null terminated, there is no need
for excessive copying of strings, such as the line name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
environments.
Please note that this can't be done while such processes run in jails.
Note: in future it would be interesting to find a way to do that
selectively for any desired proccess (choosen by user himself), probabilly
via a ptrace interface or whatever.
Obtained from: Sandvine Incorporated
Reviewed by: emaste, arch@
Sponsored by: Sandvine Incorporated
MFC: 1 month
|
|
|
|
|
|
|
| |
security.* and console.* are moved out of ftpd program block
Approved by: jhb (mentor)
MFC after: 2 weeks
|
|
|
|
| |
PR: 126934
|
|
|
|
|
| |
WARNS?=6 on amd64 but I have not tested under universe so keep WARNS?=
level as-is for now.
|
| |
|
|
|
|
| |
(more accurate extraction of Juniper Networks change)
|
|
|
|
|
|
| |
While I'm here bump WARNS to 3.
Obtained from: Juniper Networks
|
| |
|
|
|
|
|
|
|
|
|
|
| |
messages from the network. We already replace malformatted timestamps
and this option lets us replace timestamps that are correctly formatted
but wrong.
PR: 120891
Submitted by: Thomas Vogt <thomas@bsdunix.ch>
MFC after: 1 week
|
| |
|
|
|
|
| |
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
1) Use [AP]F_LOCAL rather than [AP]F_UNIX.
2) When copying a pipe's name, use f->f_un.f_pipe.f_pname, not f->f_un.f_fname.
PR: 20889
Submitted by: Damieon Stark
PR: 116642
Submitted by: Jim Pirzyk
Reviewed by: md5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for the port to drain).
+ Handle "*" as a priority properly.
+ Test what is free'ed.
+ Dynamically determine length vs. hardcoding it.
+ Free the previous message buffer (f_prevline) only after logging all the
messages and just before the process exit. Also check f_prevline for NULL
before using it.
+ The time displayed is not synchornized with the other log destinations.
+ Fix a comment.
Obtained from: Juniper Networks
|
| |
|
|
|
|
|
|
| |
PR: 95039
Sumitted by: SeaD (older version)
Reviewed by: ru
|
| |
|
| |
|
| |
|
|
|
|
|
| |
standard syslog port. This allows syslog to easily export lines of interest to
an external logging system.
|
|
|
|
|
|
|
|
|
|
|
|
| |
internal list of logfiles. So if writev(2) fails for potentially transient
errors like ENOSPC, syslogd requires a restart, even if the filesystem has
purged.
This change allows syslogd to ignore ENOSPC space errors, so that when the
filesystem is cleaned up, syslogd will automatically start logging again
without requiring the reset. This makes syslogd(8) a bit more reliable.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
when they don't exist, but sometimes its quite useful (eg. we use
non-standard log files and memory backed /var/, which is populated on
boot).
Add -C option which tells syslogd(8) to create log files if they don't
exist.
Glanced at by: phk
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
foo() {
}
to
foo()
{
}
|
|
|
|
| |
Pointy hat to: Jeremie Le Hen
|
|
|
|
| |
Submitted by: Jeremie Le Hen <jeremie le-hen org>
|
| |
|
|
|
|
|
|
|
|
| |
that have at least 3 characters.
MFC after: 1 week
Thanks to: Music band ``Chingon''
for keeping me company while searching for these.
|
|
|
|
|
|
|
|
|
| |
catch all transient errors. This fixes situations where transient
error conditions such as network interfaces losing carrier signals
or the system running out of mbufs would result in the permanent
removal of forwarding syslog messages.
MFC after: 1 week
|
|
|
|
|
| |
NI_WITHSCOPEID, and our getaddrinfo(3) does nothing special
for it, now.
|
|
|
|
|
|
|
| |
socket /var/run/logpriv.
Reviewed by: glebius and kensmith
MFC after: 2 days
|
|
|
|
|
| |
PR: bin/79260
Submitted by: Shuichi KITAGUCHI
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
addresses and scope IDs.
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
than a colon, so don't allow whitespace in program names. To be
consistent with hostnames, don't allow whitespace in the program
name specifiers in syslog.conf either.
(The first change is by Markus from the PR, the second is mine.)
PR: 68691
Submitted by: Markus Oestreicher <m.oe@x-trader.de>
MFC after: 3 weeks
|
| |
|
| |
|
| |
|
|
|
|
| |
Requested by: ru
|
|
|
|
| |
Approved by: cvs diff -b
|
|
|
|
|
|
|
|
| |
PR: bin/72366
Ok'd by: dwmalone
Approved by: julian (mentor)
Obtained from: OpenBSD
MFC after: 1 month
|