On Fri, Sep 26, 2014 at 9:01 AM, Gene Heskett <ghesk...@wdtv.com> wrote:
> On Friday 26 September 2014 08:43:58 Mark Wendt did opine > And Gene did reply: > > On Fri, Sep 26, 2014 at 8:29 AM, Gene Heskett <ghesk...@wdtv.com> wrote: > > > See subject, for a change this hits ALL the non-windows systems. > > > > > > So update your bash everywhere and reboot them ASAP. > > > > > > Cheers, Gene Heskett > > > > Yup. But no need to reboot the machine for the bash update. All you > > need to do is type 'exec bash' on any command line terminals you have > > open or log out and log back in. > > > > Mark > > I have several bash scripts that are executed and run forever at boot > time, so in order to get fresh copies into memory, a reboot is needed > here. > > But its better advice than you might think. In those systems that have an > /etc/init.d directory, those are all or nearly all bash scripts regardless > of their actual name. All of those need to be restarted using the new bash > to be assured there are no old, susceptible versions in memory. > > The point I failed to make the first time. > A reboot is still not required. Simply restart the services. Or do a 'pkill -HUP <process_name>'. Unless you are replacing the kernel on a Linux/Unix machine, there's really no need to reboot a system for something like this. Mark ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
