That is good information to know. I have solved my problems, but will try it out anyway for future reference.
Thanks, Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Tuesday, July 10, 2007 4:58 PM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: Re: [rhelv5-list] how to handle "echo" ? Collins, Kevin [MindWorks] wrote: > John, > > how would I set an ENV variable via the kernel? If I can do > that, it might just solve my problem(s). kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/ vga=794 ENV=VAL No promies, it's available to the boot script but something later might sanitize things. > > Thanks, > > Kevin > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield > Sent: Monday, July 09, 2007 6:17 PM > To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list > Subject: Re: [rhelv5-list] how to handle "echo" ? > > Collins, Kevin [MindWorks] wrote: >> Tom, >> >> this works great for "login" sessions, but it doesn't work for >> crond and rshd so I still have the problem! >> >> Actually, I found /etc/security/pam_env.conf which should work for all >> pam-enabled services, but it doesn't seem to work for either crond or >> rshd. >> >> I tried re-building the RPM from SRPM and defining _UNIV_DEFAULT=att > in >> the CCFLAGS, but it still defaults to ucb. >> >> *Sigh* - I really just want a solution that works... >> >> Kevin >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Sightler >> Sent: Friday, July 06, 2007 12:59 PM >> To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list >> Subject: RE: [rhelv5-list] how to handle "echo" ? >> >> On Fri, 2007-07-06 at 15:13 -0400, Tom Sightler wrote: >>> The echo builtin has different behavior based on setting UNIVERSE to >> ucb >>> or att. That's why I posted it as a possible workaround before, if >> you >>> can figure out a way to set it globally, which I couldn't. As it >> turns >>> out, placing echo in /usr/local/bin is simply hinting the system to >>> default to a different UNIVERSE setting. >> Well, I just found another workaround that will probably be even > better >> for us. Simple setting the envrionment variable _AST_FEATURES to >> 'UNIVERSE - att' causes echo to revert to the behavior we want (I this >> worked by calling getconf in a ksh environment but didn't know how to >> set it via an environment variable). I've added it to our > /etc/profile >> on our test system and this appears catch all of our cases. > > Setting it on the kernel commandline may work; I don't know whether > something clears the environment. > > Setting it in the environment for crond, atd etc may work too, but watch > > for reversions when the packages are updated. > > > > -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list _______________________________________________ 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
