3
As you can read in the Debian man page for daemon, it vastly depends on how you implemented your daemon under which init system.
The SysV way (stdin/out/err connected to /dev/null)
The "New-style" way : (stdout/stderr directed to systemd-journald.service)
...
10.Instead of using the syslog() call to log directly to the system syslog service, a ...
2
The syslog process typically picks up messages from three sources:
Applications, via /dev/log
Network via port 514
The kernel, via /proc/kmsg
Now the first... traditionally any application that sends to /dev/log before a syslogd process starts will have their messages lost. systemd confuses things a little because it can listen on that socket instead. ...
1
The shell command history is not an auditing tool, although misguided people may attempt to use it as such.
The audit subsystem, on the other hand, can be set to record every exec() system call and their arguments, and/or any file accesses.
You could install sudosh2 and use it as the login shell for users. It will record everything that happens in the ...
1
I have seen this behaviour after we have introduced some (large) LDAP UID numbers co-existing with "normal" UNIX UID numbers in a linux (RHEL 7) machine.
Also, in the "CAVEATS" section of the manual page for "lastlog" it states that
*"Large gaps in UID numbers will cause the lastlog program to run longer with no output to ...
Only top voted, non community-wiki answers of a minimum length are eligible
