On Friday 26 September 2014 12:23:51 Mark Wendt did opine And Gene did reply: > On Fri, Sep 26, 2014 at 12:04 PM, Gene Heskett <[email protected]> wrote: > > > Now yer sounding like a Winders user... ;-) > > > > Now thats an assault on my supposedly good sense. ;-) > > > > service --status-all |wc -l > > 44 > > > > ps -eaf|wc -l > > 265 > > > > Can you track that? I can't. > > Easy peasy. > > service --status-all | less > > ps -eaf | less > > to exit, type "q" > > I'll make a Unix/Linux sysadmin outta you yet. ;-)
Ya think? Heck, if that is how I'd have to do it, rather than less, which of course I did do at the time, I'd pipe it to | lp -dBROTHEHL2140 -, and get some exercise running to the basement to get it off that printer so I could go down the list putting a checkmark beside each process I restarted. With my bum knee, going up & down those steps one at a time using the right knee for all the bending and climbing, I'll warrant I can reboot it quicker, and KNOW the job is done right. The point being and that you seem to be missing is that every process that used bash would have to be shut down AT THE SAME TIME in order to purge the one copy of bash thats in memory, sharing a different stack pointer for each process its associated with. So I'd doubt that just going down the list with a service xyz restart would ever pull a fresh copy of the just installed version into memory, not when there is what the system thinks is a perfectly good copy of bash already in memory, locked there by 40+ other processes using it. You aren't thinking like the os thinks when you assume a simple restart of each used process will reload a fresh copy of bash per process. Simply put, tain't gonna happen. I'd go so far as to say that no os on the planet loads a separate copy of bash on a per process basis. So reboot the sucker and KNOW its done. Multi-user, multitasking os's like Unix (1970's-?) or OS9 (1982-?), never did that simply because there was not enough very expensive memory in those ancient machines to even consider loading a private copy. I can recall paying $400 for an s100 board kit with 4k of static ram on it in 1980? OS9 was my teacher about how a Unix like system worked and one of the reasons the M$ system has not been allowed to survive on the premises more than a week or 2 after I had bought the machine. And that only once, when I needed a lappy for on the road use. But it had an early Mandrake on it buy the time it hit the road the first time. This BTW is not the Mac pre-bsd OS-9, but the Microware version that first ran on a 64k, floppy based TRS-80 Color Computer. I am very familiar with that os as I did major work in several pieces of it in converting it to run on a coco which had had its cpu replaced with the considerably more intelligent Hitachi HC6309, one of the best kept secrets in computers ever. I also patched the Random Block File manager so that up to 4Gb hard drive partitions can be used, on a system that was all tapped out at 128 megs for the whole drive in the original version. Sysadmin? Yes & no. The devil is in the details, those I have to ask about, Mark, but the basic principles about how its done internally are not a puzzle, just the age creases in the faces (and blackhead locations) change according to the logo's on the box it came in. And linux has most certainly caused a population explosion with its varieties, each of which has its own preferences for "wash soap & face creams" to make it look as good as it does on the outside, with, as we all know, wildly varying degrees of success in the pretty face dept. Some of them have been Coyote Ugly over the last 16 years I've been using it. ;-) Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
