Bug#877414: systemd: please include a /var/log/README like Fedora has

2022-09-13 Thread Holger Levsen
On Mon, Sep 12, 2022 at 05:29:08PM +0200, Michael Biebl wrote:
> A "rm -f /var/log/README" in postrm is simple enough, or at least not more
> complicated then creating the symlink (manually) via debian/systemd.links.

right.
 
> Question is, what's conceptually more desired. Marco mentioned on IRC that
> shipping a static symlink in the package conflicts with the goal, that /var
> should be empty by default (see factory-reset [1]).

I don't understand, however /var/log/README is provided, it always
means /var isn't empty?

> Seems piuparts is happy with the status quo, so maybe we don't actually need
> an explicit cleanup of /var/log/README and we can just close this bug
> report?

usually piuparts is rightfully unhappy, though exceptions exist. :)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

That morning, the young barista woman told me that a customer came in with a
mask, but not wearing it. When she asked the customer to put on her mask
please, the woman said: "Why? There's no-one in here."


signature.asc
Description: PGP signature


Bug#877414: systemd: please include a /var/log/README like Fedora has

2022-09-12 Thread Michael Biebl

Am 12.09.22 um 11:59 schrieb Holger Levsen:

On Mon, Sep 12, 2022 at 11:07:06AM +0200, Michael Biebl wrote:

We could either ship this symlink directly in the package as well (so dpkg
will remove it if the package is uninstalled), or add an explicit cleanup to
systemd.postrm.


sounds like shipping the symlink is easier and thus better, isn't it?




A "rm -f /var/log/README" in postrm is simple enough, or at least not 
more complicated then creating the symlink (manually) via 
debian/systemd.links.


Question is, what's conceptually more desired. Marco mentioned on IRC 
that shipping a static symlink in the package conflicts with the goal, 
that /var should be empty by default (see factory-reset [1]).


Seems piuparts is happy with the status quo, so maybe we don't actually 
need an explicit cleanup of /var/log/README and we can just close this 
bug report?


Michael


[1] https://0pointer.net/blog/projects/stateless.html


OpenPGP_signature
Description: OpenPGP digital signature


Bug#877414: systemd: please include a /var/log/README like Fedora has

2022-09-12 Thread Holger Levsen
On Mon, Sep 12, 2022 at 11:07:06AM +0200, Michael Biebl wrote:
> We could either ship this symlink directly in the package as well (so dpkg
> will remove it if the package is uninstalled), or add an explicit cleanup to
> systemd.postrm.

sounds like shipping the symlink is easier and thus better, isn't it?


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Change is coming whether you like it or not.


signature.asc
Description: PGP signature


Bug#877414: systemd: please include a /var/log/README like Fedora has

2022-09-12 Thread Michael Biebl

On Sun, 1 Oct 2017 17:11:03 +0200 Holger Levsen  wrote:

Package: systemd
Version: 232-25+deb9u1
Severity: wishlist

Dear Maintainer,

this might be a totally bogus bug report (because I might have missed that
this is already implemented in Debian, eg I only checked stretch and a sid
schroot, but not a real sid system…), but I really like this on Fedora
systems and I think we should have it in Debian too:

[user@fedora-25 ~]$ cat /var/log/README
You are looking for the traditional text log files in /var/log, and
they are gone?

Here's an explanation on what's going on:

You are running a systemd-based OS where traditional syslog has been
replaced with the Journal. The journal stores the same (and more)
information as classic syslog. To make use of the journal and access
the collected log data simply invoke "journalctl", which will output
the logs in the identical text-based format the syslog files in
/var/log used to be. For further details, please refer to
journalctl(1).

Alternatively, consider installing one of the traditional syslog
implementations available for your distribution, which will generate
the classic log files for you. Syslog implementations such as
syslog-ng or rsyslog may be installed side-by-side with the journal
and will continue to function the way they always did.




So, what happened in the mean time is that since bullseye we do enable 
persistent logging and for bookworm the priority of rsyslog has been 
downgraded to optional, so rsyslog will no longer be installed by 
default (unless a package explicitly depends on it, which is not 
recommended)


This prompted me to revisit this bug report only to notice that my 
system already has


/var/log/README -> ../../usr/share/doc/systemd/README.logs

Apparently this is a result of

https://github.com/systemd/systemd/commit/6fe23ff31c02c7e9607edd0df819e59da5d49abc
which went unnoticed.

We could either ship this symlink directly in the package as well (so 
dpkg will remove it if the package is uninstalled), or add an explicit 
cleanup to systemd.postrm.


Thoughts?


OpenPGP_signature
Description: OpenPGP digital signature


Bug#877414: systemd: please include a /var/log/README like Fedora has

2017-10-01 Thread Holger Levsen
On Sun, Oct 01, 2017 at 10:30:32PM +0200, Michael Biebl wrote:
> There's already a bug for that. Let's block this bug accordingly

Thank you!


-- 
cheers,
Holger


signature.asc
Description: PGP signature


Bug#877414: systemd: please include a /var/log/README like Fedora has

2017-10-01 Thread Michael Biebl
Control: block -1 by 717388

Am 01.10.2017 um 22:10 schrieb Holger Levsen:
> On Sun, Oct 01, 2017 at 09:50:07PM +0200, Michael Biebl wrote:
>> Right, that's the reason why we don't install that README atm, as it
>> would be confusing. Enabling persistent logging and no longer installing
>> rsyslog by default should go hand in hand, as I don't think we really
>> want to log everything twice to disk. Once and if that happens,
>> installing the README would make sense as wel I guess.
> 
> so, should we/I retitle this bug "please enable persistent logging" or rather
> close it? :-)

There's already a bug for that. Let's block this bug accordingly


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#877414: systemd: please include a /var/log/README like Fedora has

2017-10-01 Thread Holger Levsen
On Sun, Oct 01, 2017 at 09:50:07PM +0200, Michael Biebl wrote:
> Right, that's the reason why we don't install that README atm, as it
> would be confusing. Enabling persistent logging and no longer installing
> rsyslog by default should go hand in hand, as I don't think we really
> want to log everything twice to disk. Once and if that happens,
> installing the README would make sense as wel I guess.

so, should we/I retitle this bug "please enable persistent logging" or rather
close it? :-)


-- 
cheers,
Holger


signature.asc
Description: PGP signature


Bug#877414: systemd: please include a /var/log/README like Fedora has

2017-10-01 Thread Michael Biebl
Am 01.10.2017 um 19:30 schrieb Felipe Sateler:
> On Sun, Oct 1, 2017 at 12:11 PM, Holger Levsen  wrote:
>>
>> Package: systemd
>> Version: 232-25+deb9u1
>> Severity: wishlist
>>
>> Dear Maintainer,
>>
>> this might be a totally bogus bug report (because I might have missed that
>> this is already implemented in Debian, eg I only checked stretch and a sid
>> schroot, but not a real sid system…), but I really like this on Fedora
>> systems and I think we should have it in Debian too:
> 
> Well, in debian we (still) install rsyslog by default, so that README
> would be a bit inaccurate. We don't enable persistent journal by
> default either. Maybe these two defaults should be changed? I have no
> opinion on that.

Right, that's the reason why we don't install that README atm, as it
would be confusing. Enabling persistent logging and no longer installing
rsyslog by default should go hand in hand, as I don't think we really
want to log everything twice to disk. Once and if that happens,
installing the README would make sense as wel I guess.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#877414: systemd: please include a /var/log/README like Fedora has

2017-10-01 Thread Felipe Sateler
On Sun, Oct 1, 2017 at 12:11 PM, Holger Levsen  wrote:
>
> Package: systemd
> Version: 232-25+deb9u1
> Severity: wishlist
>
> Dear Maintainer,
>
> this might be a totally bogus bug report (because I might have missed that
> this is already implemented in Debian, eg I only checked stretch and a sid
> schroot, but not a real sid system…), but I really like this on Fedora
> systems and I think we should have it in Debian too:

Well, in debian we (still) install rsyslog by default, so that README
would be a bit inaccurate. We don't enable persistent journal by
default either. Maybe these two defaults should be changed? I have no
opinion on that.

-- 
Saludos,
Felipe Sateler



Bug#877414: systemd: please include a /var/log/README like Fedora has

2017-10-01 Thread Holger Levsen
Package: systemd
Version: 232-25+deb9u1
Severity: wishlist

Dear Maintainer,

this might be a totally bogus bug report (because I might have missed that
this is already implemented in Debian, eg I only checked stretch and a sid
schroot, but not a real sid system…), but I really like this on Fedora
systems and I think we should have it in Debian too:

[user@fedora-25 ~]$ cat /var/log/README
You are looking for the traditional text log files in /var/log, and
they are gone?

Here's an explanation on what's going on:

You are running a systemd-based OS where traditional syslog has been
replaced with the Journal. The journal stores the same (and more)
information as classic syslog. To make use of the journal and access
the collected log data simply invoke "journalctl", which will output
the logs in the identical text-based format the syslog files in
/var/log used to be. For further details, please refer to
journalctl(1).

Alternatively, consider installing one of the traditional syslog
implementations available for your distribution, which will generate
the classic log files for you. Syslog implementations such as
syslog-ng or rsyslog may be installed side-by-side with the journal
and will continue to function the way they always did.

Thank you!

Further reading:
man:journalctl(1)
man:systemd-journald.service(8)
man:journald.conf(5)
http://0pointer.de/blog/projects/the-journal.html
[user@fedora-25 ~]$

Thanks for maintaining systemd!


-- 
cheers,
Holger


signature.asc
Description: PGP signature