Re: Sean Whitton > > Right, but times are changing. In the past, fail2ban could depend on > > system-log-daemon and expect files in /var/log/ to appear, but > > systemd/journalctl keep things elsewhere. > > > > Perhaps that is the issue we should be discussing? > > What issue exactly do you mean? I'm asking because what you describe > does seem to be the issue we are discussing, to me.
What exactly can a package expect to get when depending on system-log-daemon? 1) /dev/log exists and messages can be posted 2) messages appear in /var/log/something (with some amount of standardized filenames) 3) there is some way to emit log messages that the admin can read Afaict the OP's use case is actually the generic 3) case. (vpns should be able to log messages) fail2ban would want 2) (it doesn't care how messages get there). Everyone in this thread seems to assume that we are talking about 1). The classic sysloggers implement 1) 2) 3). journald implements 1) and 3), and we consider that ok. So loosely speaking, the only package in the archive that has a legitimate use case to depend on logging (fail2ban) depends on something that journald does not provide. Christoph
