3 ms·
Don't like it? Just drop the calls to pam_motd.so from /etc/pam.d/login. Done.
by rlpb 10y ago
Don't like it? Just drop the calls to pam_motd.so from /etc/pam.d/login. Done.
- prodigal_erik 10y agoIt looks like that also skips displaying /etc/motd. If you just want to skip regenerating /var/run/motd, you have to blow away /etc/update-motd.d but continue running pam_motd.so because it's bizarrely responsible for both.
- eropple 10y agoI feel obligated to point out that having to "just" do that is kind of really insane. Making the default provide effectively useless information (nobody's gonna scroll back to read that motd for an IP address and it sure doesn't replace running htop for system info), and then making actually fixing the original mistake difficult and annoying, is not a good look. Also, as the sibling notes, this kills MOTDs entirely, not because for some reason we need to bolt this whole contraption together and then not really document it at all. Ubuntu!
- voidz 10y agoYou use a lot of words. Insane? It is actually quite the opposite, pam is where the author should have started. Not knowing about pam and refusing to learn about it, as a server administrator: if I ever would call something insane..
- eropple 10y agoOne of us has written PAM modules that are being used in production environments and the other one of us is you. I still wouldn't think to look there if I didn't happen to recall, in my junk drawer of Stuff I Shouldn't Need To Know But Do Anyway Because System Administration Is Bullshit, that pam_motd.so is a thing. And it gets better: by cavalierly modifying that, you would have been wrong besides; you just turned off MOTDs, not controlled them, because that is the update-motd horrorshow's job. So explain to me why any of this matters to the problem at hand in the first place?
- CaptSpify 10y agoWhy does the motd need any interaction with pam? Those are two completely separate things
- rlpb 10y ago> Making the default provide effectively useless information... That's quite presumptuous I think. You may find it effectively useless. Others may not. The job of a default is to cater for a majority. One size does not fit all, so it is certain that there will exist people unhappy about the default whatever it is. So just because some number of people complain does not mean that the default is wrong. On the other hand, I accept the documentation could be improved, but this does generally need someone other than the author to point out deficiencies. The author could have written and submitted a documentation patch in the time it took him to write that blog post.
- dingaling 10y agoMaking changes in PAM is never trivial. One error and users are locked-out.
- digi_owl 10y agoMore and more i see why Slackware has yet to adopt PAM support.