Re: Networking / Kill Questions

From: Arthur Hagen (art_at_broomstick.com)
Date: 10/16/04 

Date: Fri, 15 Oct 2004 19:12:15 -0400

houghi <houghi@houghi.org.invalid> wrote:
>
> They will also have a discusion on how to do this: perl, bash, sh,
> whatever and what the advantages and disadvatages are of each and
> every line of code.

Absolutely not. Writing scripts in bash is something a real sysadmin would
*never* consider, again for portability reasons.

> For me, it is there and I use it. For you, you an do it in another
> way. That is the power of Linux. You make the choice. For others who
> did not know it was there, now they do and can decide for themselves.
> Like many things it is not OR/OR it is AND/AND

Except that one of the ANDs lead to a habit that will have you stumped if
you ever find yourself on a different system. That's why I prefer to
recommend the habits most compatible with ALL systems, not just SuSE.

Regards, 

-- 
*Art

Relevant Pages

  • Re: run cron every four weeks?
    ... >> I think a more realistic comparison would involve using bash and various utilities or C programs (which is where sensible people go when bash etc. aren't ... >> enough) instead of perl on that desktop. ... > The perl program uses less non-shared resources. ... > in memory, except the perl executable, the bash executable, and perl's libperl.so. ...
    (comp.sys.hp.hpux)
  • Re: run cron every four weeks?
    ... >> I think a more realistic comparison would involve using bash and various utilities or C programs (which is where sensible people go when bash etc. aren't ... >> enough) instead of perl on that desktop. ... > The perl program uses less non-shared resources. ... > in memory, except the perl executable, the bash executable, and perl's libperl.so. ...
    (comp.unix.questions)
  • Re: run cron every four weeks?
    ... >> I think a more realistic comparison would involve using bash and various utilities or C programs (which is where sensible people go when bash etc. aren't ... >> enough) instead of perl on that desktop. ... > The perl program uses less non-shared resources. ... > in memory, except the perl executable, the bash executable, and perl's libperl.so. ...
    (comp.unix.programmer)
  • Re: run cron every four weeks?
    ... >> I think a more realistic comparison would involve using bash and various utilities or C programs (which is where sensible people go when bash etc. aren't ... >> enough) instead of perl on that desktop. ... > The perl program uses less non-shared resources. ... > in memory, except the perl executable, the bash executable, and perl's libperl.so. ...
    (comp.sys.sun.admin)
  • Re: run cron every four weeks?
    ... > Package: bash ... > Priority: required ... > And perl needs a bunch of support packages that bash doesn't. ...
    (comp.unix.programmer)