-
Expected behavior
Secure Remote logging to the server without the getting any messages like below
Actual behavior
getting the messages like below :
Message from syslogd@system-99 at Jan 16 01…
-
For privacy and disk space.
Thx!
-
**[MANDATORY] Describe the bug [MANDATORY]**
I upgraded my system from 13.3 to 14.1-RELEASE, including pkg-static update -f.
I have run bastille bootstrap 14.1-RELEASE.
When I update a jail by ch…
-
**[MANDATORY] Describe the bug [MANDATORY]**
If your Bastillefile contains more than one space in one line this block:
https://github.com/BastilleBSD/bastille/blob/b85d6347dee44c943819c2d7b4eee9c5a3…
-
The output is unnecessary and disturbing for a normal boot. It should be silenced, and just display success or error result.
-
Hello,
Could I suggest monitoring UDP/TCP port like syslog.
Thanx.
-
Hi,
rsyslog 8.19 with lookup-table seems to have a bug related to restart of rsyslog daemon.
Sometimes the following error message appears:
syslogd[19120]: segfault at 7fc21a3b89d0 ip 00007fc21f844…
-
Hi! in the code below, the SIGPIPE handler is set to avoid `write` failures, but I see this is not really good practice for servers (see https://stackoverflow.com/a/7777789/515485 for example).
This…
-
Chris Hoffman has an idea for a high-level diagnostic tool that would see various kinds of high-level log messages, which it would try to abstract into system health evaluations. The idea is that our…
-
### Describe the bug
A lot of apparmor tools doesn't work because they can't find a python module.
### Steps To Reproduce
Steps to reproduce the behavior:
1. `security.apparmor.enable = true;`
…