No worries from my point of view, they are all related messages. If you open a bug on pam_env, let me know and I'll update it with a "me too"...
I think I like that as the best choice. Thanks, Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Sightler Sent: Tuesday, July 10, 2007 8:55 PM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: RE: [rhelv5-list] how to handle "echo" ? I'm replying to two emails in one, hope that's not too bad. On Tue, 2007-07-10 at 09:29 -0700, Collins, Kevin [MindWorks] wrote: > >Yeah, that looks like it should work. Both cron and rsh appear to > >properly call pam_env. It's interesting that it didn't. I'll try to > >set it up on our test server tomorrow just to verify your results. > > I actually found a report of a bugfix in FC6 for rshd NOT correctly > loading the pam_env and the revision of rshd is one higher than what > is > in RHEL5 (rsh-server-0.17-38 vs rsh-server-0.17-37). This actually appears to be a bug in RHEL5 and pam_env.so rather than rsh itself. I tested by adding a simple environment to /etc/security/pam_env.conf on a RHEL4 and RHEL5 box. This should technically set the environment for all pam enable services, which is practically all logins, including ssh. Well, on the RHEL4 box it works as expected. I can set or override any environment I want, console, ssh, rsh, pretty much anything. Doing the exact same thing on a RHEL5 box and I can't make this work at all, for ssh, or local logins, much less rsh. I'll probably open a bug/service request on this issue. On Tue, 2007-07-10 at 15:22 -0700, Collins, Kevin [MindWorks] wrote: > Well, I was able to make the recompile work by creating a wrapper > script > for /bin/echo to trick the test below. I renamed /bin/echo to > /bin/echo.orig and then created a /bin/echo script that does 'exec > /bin/echo.orig -e $@'. > > Once the build was done, I put the original echo back. This is a good > enough solution for me as now the default behavior is "att". I thought that would probably work, glad to know it did. As we get further along in our test we might have to do something similar if we hit additional issues, even though I would hate to have to support this package separately. Later, Tom _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
