http://bugzilla.opensuse.org/show_bug.cgi?id=1204434 http://bugzilla.opensuse.org/show_bug.cgi?id=1204434#c6 --- Comment #6 from Luciano Santos <luc14n0@opensuse.org> --- (In reply to C J from comment #4)
(In reply to Luciano Santos from comment #3)
That's why we have manpages for:
$ man environment
1. I worked before and stopped after an update. -> Who would think to look into the cli man?
2.The command "environment" doesn't exit. -> Who would think to look into the cli man?
But thanks for the feedback. Glad I could learn something today.
Yes. Usually, configuration files have their own manpage, under section 5 [1]. You were using a wrong syntax in the first place. Yes, it was working before, but at the risk of happening what you experienced. In Leap 15.4 we have:
$ rpm -q pam pam-1.3.0-150000.6.58.3.x86_64 $ cat /etc/environment # # This file is parsed by pam_env module # # Syntax: simple "KEY=VAL" pairs on separate lines #
And, in Tumbleweed:
$ rpm -q pam pam-1.5.2-8.1.x86_64 $ cat /etc/environment # # This file is parsed by pam_env module # # Syntax: simple "KEY=VAL" pairs on separate lines #
The syntax is still the same: "KEY=VAL". And, yes, the latest update to the PAM package brought a new patch that seems to be, enforcing the expected syntax now. [1] https://www.commandlinux.com/man-page/man5/ -- You are receiving this mail because: You are on the CC list for the bug.