Re: Deterministic delays in POSIX shell scripts (Was: Re: notify via virtual terminal available packages)

On Fri 25 Sep 2020 at 12:28:31 (+), Andy Smith wrote: > On Fri, Sep 25, 2020 at 07:49:19AM -0400, Greg Wooledge wrote: > > On Fri, Sep 25, 2020 at 07:44:25AM +, Andy Smith wrote: > > > "hostid" tends to return a hexadecimal representation of the first > > > IPv4 address (but isn't guarantee

Re: Deterministic delays in POSIX shell scripts (Was: Re: notify via virtual terminal available packages)

Hello, On Fri, Sep 25, 2020 at 07:49:19AM -0400, Greg Wooledge wrote: > On Fri, Sep 25, 2020 at 07:44:25AM +, Andy Smith wrote: > > "hostid" tends to return a hexadecimal representation of the first > > IPv4 address (but isn't guaranteed to). > > unicorn:~$ hostid > 007f0101 > > Doesn't look

Re: Deterministic delays in POSIX shell scripts (Was: Re: notify via virtual terminal available packages)

On Fri, Sep 25, 2020 at 07:44:25AM +, Andy Smith wrote: > "hostid" tends to return a hexadecimal representation of the first > IPv4 address (but isn't guaranteed to). unicorn:~$ hostid 007f0101 Doesn't look very useful. That's just 127.0.1.1 in a 16-bit little endian format. > On a systemd

Deterministic delays in POSIX shell scripts (Was: Re: notify via virtual terminal available packages)

Hello, On Thu, Sep 24, 2020 at 08:49:07AM -0600, Charles Curley wrote: > On Thu, 24 Sep 2020 10:38:55 -0400 > Greg Wooledge wrote: > > So you're just doing "sleep 1" every time. > > Ah, thank you. Yup. Which is weird, because it worked when I first > wrote that many years ago. In cron scripts w

Re: Looping Shell Scripts and System Load

On Thu, 25 Jun 2020 at 19:23, Tixy wrote: > On Wed, 2020-06-24 at 13:43 -0400, Greg Wooledge wrote: > [Lots of good shell scripting advice snipped] > Thanks Greg for posting these code reviews of people's scripts, it's > not just the script authors which might learn something, but also some > of

Re: Looping Shell Scripts and System Load

On Wed, 2020-06-24 at 13:43 -0400, Greg Wooledge wrote: [Lots of good shell scripting advice snipped] Thanks Greg for posting these code reviews of people's scripts, it's not just the script authors which might learn something, but also some of us list subscribers. :-) -- Tixy

Re: Looping Shell Scripts and System Load

Greg Wooledge writes: > All-caps names are reserved for environment variables (HOME, PATH), > and internal shell variables (IFS, PWD, HISTFILE). > > Avoiding all-caps names allows you to avoid collisions with a variable > name that might be used for something else. Most of the time. This > bein

Re: Looping Shell Scripts and System Load

rt 3 unzip processes. This directory had 13 zip files and the first 2 or 3 roared to life and then things slowed down as they all tried to run. I expected this and I've been doing unix shell scripts for literally 31 years this Summer so it is no mystery as each new job spawns a whol

Re: Looping Shell Scripts and System Load

Greg Wooledge writes: > On Wed, Jun 24, 2020 at 08:23:18PM +0200, Roger Price wrote: >> On Wed, 24 Jun 2020, Greg Wooledge wrote: >> >> > > MEDIADIR=`pwd` >> > >> > Don't use all caps variable names. >> >> Without getting into syntax-religious wars, what is the reasoning behind >> this recomme

Re: Looping Shell Scripts and System Load

On Wed, Jun 24, 2020 at 08:23:18PM +0200, Roger Price wrote: > On Wed, 24 Jun 2020, Greg Wooledge wrote: > > > > MEDIADIR=`pwd` > > > > Don't use all caps variable names. > > Without getting into syntax-religious wars, what is the reasoning behind > this recommendation? Roger All-caps names ar

Re: Looping Shell Scripts and System Load

On Wed, 24 Jun 2020, Greg Wooledge wrote: MEDIADIR=`pwd` Don't use all caps variable names. Without getting into syntax-religious wars, what is the reasoning behind this recommendation? Roger

Re: Looping Shell Scripts and System Load

Martin McCormick wrote on 6/24/20 11:19 AM: > > Right now, uptime looks like: > > 11:48:07 up 26 days, 23:10, 7 users, load average: 16.15, 15.60, 10.65 > > That's pretty loaded so ideally, one could start the > looping script and it would fire up processes until things got > rea

Re: Looping Shell Scripts and System Load

On Wed, Jun 24, 2020 at 01:24:23PM -0400, Roberto C. Sánchez wrote: > I recommend you look at the parallel package. It is specifically geared > toward parallelization of constructed shell command lines. Think > something along the lines of "find -exec " but with the ability > to parallel

Re: Looping Shell Scripts and System Load

On Wed, Jun 24, 2020 at 12:19:30PM -0500, Martin McCormick wrote: > #!/bin/sh Why? Use bash. > unarchive () { > unzip $1 Quotes. > MEDIADIR=`pwd` Don't use all caps variable names. Don't use backticks. Use $() for command substitution. Don't use $(pw

Re: Looping Shell Scripts and System Load

On Wed, Jun 24, 2020 at 12:19:30PM -0500, Martin McCormick wrote: > I wrote a shell script that unzips documents and I originally > wrote it such that it gets document #1, unzips it then gets > document #2, etc and it does that just fine so I wondered if I > could make it run faster by starting sev

Looping Shell Scripts and System Load

iles and the first 2 or 3 roared to life and then things slowed down as they all tried to run. I expected this and I've been doing unix shell scripts for literally 31 years this Summer so it is no mystery as each new job spawns a whole new set of processes to unzip the file it is workin

Re: OT: How to get Dot files out of the way via shell scripts

On Wed, Jul 17, 2013 at 06:37:44PM +0100, Lisi Reisz wrote: > Thanks. That is really interesting - I love linguistics and etymology. But > this is an English language list. ;-) > > Lisi Well, when you pop an 'outlandish' bottle, the outcoming (imp) might not comply with 'inlandish' rules.. ;-)

Re: OT: How to get Dot files out of the way via shell scripts

Am 17.07.2013 um 06:24 schrieb Doug: Doggpne! Just when I begin to think my German is not bad, something like this comes along! (It's not the first time. Quite some years ago I was sent to Germany on business, to Stuttgart. Schwäbisch, Suabian Listening to the people in that area speak

Re: OT: How to get Dot files out of the way via shell scripts

On Wednesday 17 July 2013 16:12:58 Wilko Fokken wrote: > On Wed, Jul 17, 2013 at 03:18:33AM +0200, Ralf Mardorf wrote: > > On Wed, 2013-07-17 at 03:13 +0200, Ralf Mardorf wrote: > > > PPS: "Guten Tag miteinander!" or "Hallo miteinander!" or "Hallo > > > zusammen!" > > > > > > Resp. "Moin" is indepe

Re: OT: How to get Dot files out of the way via shell scripts

On Wed, Jul 17, 2013 at 03:18:33AM +0200, Ralf Mardorf wrote: > On Wed, 2013-07-17 at 03:13 +0200, Ralf Mardorf wrote: > > PPS: "Guten Tag miteinander!" or "Hallo miteinander!" or "Hallo zusammen!" > > > > Resp. "Moin" is independent of the daytime, so it's the German "Hallo", > > Aaaarghhh, my b

Re: OT: How to get Dot files out of the way via shell scripts

On Wed, 17 Jul 2013 06:24:46 +0200, Doug wrote: Doggpne! Just when I begin to think my German is not bad, something like this comes along! (It's not the first time. Quite some years ago I was sent to Germany on business, to Stuttgart. Listening to the people in that area speak among themselves,

Re: OT: How to get Dot files out of the way via shell scripts

On 07/16/2013 09:07 PM, Ralf Mardorf wrote: > On Wed, 2013-07-17 at 02:42 +0200, Ralf Mardorf wrote: >> On Tue, 2013-07-16 at 23:36 +0100, Lisi Reisz wrote: >>> On Thursday 11 July 2013 06:12:35 Wilko Fokken wrote: Moin mitnanner, >>> >>> Could some kind person please translate this for me? >>

Re: OT: How to get Dot files out of the way via shell scripts

On Wed, 2013-07-17 at 03:13 +0200, Ralf Mardorf wrote: > PPS: "Guten Tag miteinander!" or "Hallo miteinander!" or "Hallo zusammen!" > > Resp. "Moin" is independent of the daytime, so it's the German "Hallo", Aaaarghhh, my broken English sucks. Not "Hallo" is misinterpreted, but "Moin". > someti

Re: OT: How to get Dot files out of the way via shell scripts

PPS: "Guten Tag miteinander!" or "Hallo miteinander!" or "Hallo zusammen!" Resp. "Moin" is independent of the daytime, so it's the German "Hallo", sometimes misinterpreted for "Guten Morgen" (Good morning!) only, but it's for "Guten Tag" (Good day!) and "Guten Abend!" (Good evening!) etc. too. -

Re: OT: How to get Dot files out of the way via shell scripts

On Wed, 2013-07-17 at 02:42 +0200, Ralf Mardorf wrote: > On Tue, 2013-07-16 at 23:36 +0100, Lisi Reisz wrote: > > On Thursday 11 July 2013 06:12:35 Wilko Fokken wrote: > > > Moin mitnanner, > > > > Could some kind person please translate this for me? > > (although it looks German to me) > > It is

OT: How to get Dot files out of the way via shell scripts

On Tue, 2013-07-16 at 23:36 +0100, Lisi Reisz wrote: > On Thursday 11 July 2013 06:12:35 Wilko Fokken wrote: > > Moin mitnanner, > > Could some kind person please translate this for me? > (although it looks German to me) It is German. "Moin" is for "Hello". "mitnanner" is for "everyone", from t

Re: How to get Dot files out of the way via shell scripts

On Thursday 11 July 2013 06:12:35 Wilko Fokken wrote: > Moin mitnanner, Could some kind person please translate this for me? I have Googled for a translation, but apart from a suggestion that it was probably Finnish (although it looks German to me), I am none the wiser. I tried Wiktionary, bu

Re: How to get Dot files out of the way via shell scripts

On Thu, Jul 11, 2013 at 08:05:51PM +0200, Martin Steigerwald wrote: > Am Donnerstag, 11. Juli 2013, 09:55:20 schrieb Andrei POPESCU: > > > append command:"cd"to .profile > > > > > > > > > > > > > > > 3. Modify /etc/passwd: login_dir ==> /home//.rc > >

Re: How to get Dot files out of the way via shell scripts

On Thu, Jul 11, 2013 at 08:05:51PM +0200, Martin Steigerwald wrote: > Am Donnerstag, 11. Juli 2013, 09:55:20 schrieb Andrei POPESCU: > > > append command:"cd"to .profile > > > > > > > > > > > > > > > 3. Modify /etc/passwd: login_dir ==> /home//.rc > >

Re: How to get Dot files out of the way via shell scripts

Am Donnerstag, 11. Juli 2013, 09:55:20 schrieb Andrei POPESCU: > > append command:"cd"to .profile > > > > > > > > > > 3. Modify /etc/passwd: login_dir ==> /home//.rc > > == > > > > exam

Re: How to get Dot files out of the way via shell scripts

On Thu, Jul 11, 2013 at 09:55:20AM +0300, Andrei POPESCU wrote: > On Jo, 11 iul 13, 07:12:35, Wilko Fokken wrote: > > > > The following lines explain, what should be done in order to get the dot > > files out of the way into a subdirectory. > > You included lots of unrelated customizations, see b

Re: How to get Dot files out of the way via shell scripts

On Jo, 11 iul 13, 07:12:35, Wilko Fokken wrote: > > The following lines explain, what should be done in order to get the dot > files out of the way into a subdirectory. You included lots of unrelated customizations, see below. > The dot files of root go into subdir "/root/" Err, aren't they al

Re: How to get Dot files out of the way via shell scripts

On Mon, Jul 08, 2013 at 04:55:55PM +0200, ha wrote: > Thanks Ralph, I guess it would do it. > But I didn't plan to separate the conf files completely, I was hoping > for a solution more alike Wilko's (if it works). > After all we all have .config file in our home directory. > It makes sense that

Re: OT: quoting variable names in shell scripts

Kamaraju writes: > I am wondering if there is a way to rewrite the names variable in > stanza2 such that the output from stanza 1 and stanza 2 are the same. I can think of several, but I doubt any will do what you want. What is your actual problem? What are you trying to achieve? -- John Hasler

Re: OT: quoting variable names in shell scripts

On Thu, Jul 7, 2011 at 10:31 AM, Teemu Likonen wrote: > * 2011-07-07T07:13:24+02:00 * Javier Barroso wrote: > >> On Thu, Jul 7, 2011 at 5:22 AM, Kamaraju S Kusumanchi >> wrote: >>> Consider the following shell script > >>> #! /bin/sh > >> You can use array variables if you want: >> >> names=("kam

Re: OT: quoting variable names in shell scripts

* 2011-07-07T07:13:24+02:00 * Javier Barroso wrote: > On Thu, Jul 7, 2011 at 5:22 AM, Kamaraju S Kusumanchi > wrote: >> Consider the following shell script >> #! /bin/sh > You can use array variables if you want: > > names=("kama" "raju" "k a m a") > for i in "${names[@]}" Yes, but not with /b

Re: OT: quoting variable names in shell scripts

On Thu, Jul 7, 2011 at 5:22 AM, Kamaraju S Kusumanchi wrote: > Consider the following shell script > > $cat manual_listing.sh > #! /bin/sh > > # stanza 1 > for i in "kama" "raju" "k a m a" "r a j u" > do >        echo $i > done > > # stanza 2 > names='kama raju' > for i in $names > do >        ech

Re: OT: quoting variable names in shell scripts

On 07/06/11 at 11:22pm, Kamaraju S Kusumanchi wrote: > Consider the following shell script > > $cat manual_listing.sh > >

OT: quoting variable names in shell scripts

Consider the following shell script $cat manual_listing.sh #! /bin/sh # stanza 1 for i in "kama" "raju" "k a m

Re: How to make Konqueror open shell scripts in an editor instead of running them

On Mar 19, 4:20 am, Joe Hart <[EMAIL PROTECTED]> wrote: > Adam Porter wrote: > > A few minutes of googling found this very useful tip. If you want Konqueror > > to open shell scripts in an editor instead of running them (usually in the > > background, which isn'

Re: How to make Konqueror open shell scripts in an editor instead of running them

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adam Porter wrote: > A few minutes of googling found this very useful tip. If you want Konqueror > to open shell scripts in an editor instead of running them (usually in the > background, which isn't usually very useful), just add the

How to make Konqueror open shell scripts in an editor instead of running them

A few minutes of googling found this very useful tip. If you want Konqueror to open shell scripts in an editor instead of running them (usually in the background, which isn't usually very useful), just add the x-shellscript MIME type to the text group in Konqueror's file associatio

Re: Portable shell scripts

csj <[EMAIL PROTECTED]> writes: > I tend to write scripts which are tcsh-compatible. So > "#!/bin/tcsh". But its somewhat a waste of effort to write one > set of scripts for bash and another for tcsh. My main problem is > handling the variables. Is there a shell-portable way to specify > varia

Re: Portable shell scripts

On Wed, Nov 12, 2003 at 09:24:04AM +0800, csj wrote: > I tend to write scripts which are tcsh-compatible. So > "#!/bin/tcsh". Wow. You're mad. Sorry :) The C shell is too broken for serious scripting. > But its somewhat a waste of effort to write one set of scripts for > bash and another for tcs

Re: Portable shell scripts

On Mon, 10 Nov 2003 23:18:56 -0700, Bob Proulx wrote: > > csj wrote: > > Is there a way to write portable shell scripts. In > > particular, I've problems with built-ins setenv (tcsh) and > > export (bash). How do I define variables in tcsh and have > > them

Re: Portable shell scripts

csj wrote: > Is there a way to write portable shell scripts. In particular, > I've problems with built-ins setenv (tcsh) and export (bash). > How do I define variables in tcsh and have them usable in bash > too? Your best option is "#!/bin/sh" at the top of all of

Re: Portable shell scripts

On Mon, Nov 10, 2003 at 07:15:56AM +0800, csj wrote: > Is there a way to write portable shell scripts. In particular, > I've problems with built-ins setenv (tcsh) and export (bash). > How do I define variables in tcsh and have them usable in bash > too? I don't believe

Portable shell scripts

Is there a way to write portable shell scripts. In particular, I've problems with built-ins setenv (tcsh) and export (bash). How do I define variables in tcsh and have them usable in bash too? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". T

Re: (OT) exec nonreadable shell scripts

On Wed, Jan 10, 2001 at 09:31:21PM -0500, D-Man wrote: ... > I recall seeing somewhere that with the new interpreter, .pyo files > can be executed (by the interpreter, but by calling the file not the > interpreter). Maybe not. I wish I could remember where I saw > that. It doesn't work here wit

Re: (OT) exec nonreadable shell scripts

On Wed, Jan 10, 2001 at 09:31:21PM -0500, D-Man wrote: > I recall seeing somewhere that with the new interpreter, .pyo files > can be executed (by the interpreter, but by calling the file not the > interpreter). Maybe not. I wish I could remember where I saw > that. I doubt it. My understandin

Re: (OT) exec nonreadable shell scripts

On Thu, Jan 11, 2001 at 01:47:14AM +0100, Carel Fellinger wrote: | On Mon, Jan 10, 2000 at 04:04:14AM -0500, D-Man wrote: | > On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote: | > | would writing scripts in a compiled language like | > | C be a solution? | > | | > | > If any binary files c

Re: (OT) exec nonreadable shell scripts

On Mon, Jan 10, 2000 at 04:04:14AM -0500, D-Man wrote: > On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote: > | would writing scripts in a compiled language like > | C be a solution? > | > > If any binary files can be exec as suid, then I would recommend > python. It will have more of the

Re: (OT) exec nonreadable shell scripts

On Wed, Jan 10, 2001 at 10:42:22AM -0800, brian moore wrote: > On Wed, Jan 10, 2001 at 06:24:33PM +, Rick wrote: > > sorry for off-topic, but I've been banging my head trying to set up shell > > scripts that can be executed but not read by a user. > > Not doabl

Re: (OT) exec nonreadable shell scripts

On Wed, Jan 10, 2001 at 06:24:33PM +, Rick wrote: > sorry for off-topic, but I've been banging my head trying to set up shell > scripts that can be executed but not read by a user. > > Basically, for test.sh : > > #!/usr/bin/bash > echo hullo! > > *** &

Re: (OT) exec nonreadable shell scripts

On Mon, Jan 10, 2000 at 04:04:14AM -0500, D-Man wrote: > On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote: > | would writing scripts in a compiled language like > | C be a solution? > | > Errm .. then they are not scripts anymore... Cliff > If any binary files can be exec as suid, then I

Re: (OT) exec nonreadable shell scripts

On Mon 10 Jan 00, 4:04 AM, D-Man said... > On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote: > | would writing scripts in a compiled language like > | C be a solution? > | > > If any binary files can be exec as suid, then I would recommend > python. It will have more of the feel of a scr

Re: (OT) exec nonreadable shell scripts

On Wed, Jan 10, 2001 at 11:27:38AM -0800, Xucaen wrote: | would writing scripts in a compiled language like | C be a solution? | If any binary files can be exec as suid, then I would recommend python. It will have more of the feel of a script with its high level view of things. Python programs

Re: (OT) exec nonreadable shell scripts

ht to sudo or suid but > maybe letting users read the script is okay. > So much for security through > obscurity ;) > > thanks again > rick > > brian moore writes: > > > On Wed, Jan 10, 2001 at 06:24:33PM +, > Rick wrote: > > > sorry for off-topic, b

Re: (OT) exec nonreadable shell scripts

but I've been banging my head trying to set up shell > > scripts that can be executed but not read by a user. > > Not doable. > > The shell needs to read them in order to execute them. > > (Well, you could do something REALLY evil like suid wrappers switching >

Re: (OT) exec nonreadable shell scripts

On Wed, Jan 10, 2001 at 06:24:33PM +, Rick wrote: > sorry for off-topic, but I've been banging my head trying to set up shell > scripts that can be executed but not read by a user. Not doable. The shell needs to read them in order to execute them. (Well, you could do something

Re: (OT) exec nonreadable shell scripts

Rick wrote: > > sorry for off-topic, but I've been banging my head trying to set up shell > scripts that can be executed but not read by a user. > > Basically, for test.sh : > > #!/usr/bin/bash > echo hullo! > > *** > [EMAIL PROTECTED]:~]$ chmod 111 tes

(OT) exec nonreadable shell scripts

sorry for off-topic, but I've been banging my head trying to set up shell scripts that can be executed but not read by a user. Basically, for test.sh : #!/usr/bin/bash echo hullo! *** [EMAIL PROTECTED]:~]$ chmod 111 test.sh [EMAIL PROTECTED]:~]$ ./test.sh ./test.sh: ./test.sh: Permi

Re: execution of shell scripts from cdrom

On Tue, Nov 07, 2000 at 10:37:02AM +0100, Danny Lathouwers wrote: > Dear community, > > I wanted to execute a shell script from /cdrom and it fails with the > following message: > bash: ./scriptname: Permission denied. > The script is executable and is run as root, so should work. > Copying the s

execution of shell scripts from cdrom

Dear community,   I wanted to execute a shell script from /cdrom and it fails with the following message: bash: ./scriptname: Permission denied. The script is executable and is run as root, so should work. Copying the script to ~ works but i really need to run it from /cdrom. Does this have a

Re: where to put shell scripts?

On Tue, Oct 31, 2000 at 08:58:19PM -0500, Brenda J. Butler wrote: > > Also, if you have split out your filesystem such that /usr/anything > is mounted, then in the event of a system crash your /usr/lib dynamic > libraries may not be available if those filesystems refuse to mount. > This is a compe

Re: where to put shell scripts?

it is standalone (can work even if all the other dirs (except perhaps /tmp, and perhaps even that should not be insurmountable) are unavailable to it), _and_ if you need it to re-establish your system after a crash, it can go in /bin or /sbin. Otherwise it goes in /usr/bin or /usr/sbin. Shell s

Re: where to put shell scripts?

In article <[EMAIL PROTECTED]>, William T Wilson <[EMAIL PROTECTED]> wrote: >I also question the historical accuracy of 'sbin' as "static binary" - >Unix has always had /sbin, but it hasn't always had dynamic linking. How soon they forget. Not all Unices have always had /sbin. Not even Linux. In

Re: where to put shell scripts?

On Tue, 31 Oct 2000, Bud Rogers wrote: > I think it could be argued that those changes are not necessarily good > from the standpoint of system security. In the modern world, sbin really does mean "system" binaries. The division between "things you need to fix a crashed system" and "things for o

Re: where to put shell scripts?

On Tue, 31 Oct 2000, Sean 'Shaleh' Perry wrote: > > Current practice seems to have strayed a bit from the concept of only > > having statically linked binaries in the sbin directories. You may find > > shell scripts, perl, python, all kinds of stuff. I think these d

Re: where to put shell scripts?

> > Current practice seems to have strayed a bit from the concept of only having > statically linked binaries in the sbin directories. You may find shell > scripts, perl, python, all kinds of stuff. I think these days a lot of > people tend to think the 's' stands

Re: where to put shell scripts?

On Tue, 31 Oct 2000, Sean 'Shaleh' Perry wrote: > On 31-Oct-2000 Krzys Majewski wrote: > > I have a habit of writing many shell scripts for everything. Some of > > them are very local to me, so I put them in ${HOME}/shell and stick > > that in my PATH. Some o

Re: where to put shell scripts?

Krzys Majewski wrote: > > I have a habit of writing many shell scripts for everything. Some of > them are very local to me, so I put them in ${HOME}/shell and stick > that in my PATH. Makes sense. > Some of them may be generally useful, so although I > don't h

RE: where to put shell scripts?

On 31-Oct-2000 Krzys Majewski wrote: > I have a habit of writing many shell scripts for everything. Some of > them are very local to me, so I put them in ${HOME}/shell and stick > that in my PATH. Some of them may be generally useful, so although I > don't have any users,

where to put shell scripts?

I have a habit of writing many shell scripts for everything. Some of them are very local to me, so I put them in ${HOME}/shell and stick that in my PATH. Some of them may be generally useful, so although I don't have any users, I'm anal, and I put them in /usr/local/sbin/. I d

Re: complex shell scripts

I am looking to understand the everyday admin of unix and how people put > > together the common commands into compound/complex shell scripts. > > > > does anybody know of a good place for samples (this is how you import > > users form a text file or some such thing) >

Re: complex shell scripts

On Wed, Sep 13, 2000 at 10:06:48AM -0400, Mark Simos ([EMAIL PROTECTED]) wrote: > I am looking to understand the everyday admin of unix and how people put > together the common commands into compound/complex shell scripts. > > does anybody know of a good place for samples (this is ho

Re: complex shell scripts

On Wed, Sep 13, 2000 at 10:06:48AM -0400, Mark Simos wrote: > I am looking to understand the everyday admin of unix and how people put > together the common commands into compound/complex shell scripts. > > does anybody know of a good place for samples (this is how you import > us

complex shell scripts

I am looking to understand the everyday admin of unix and how people put together the common commands into compound/complex shell scripts. does anybody know of a good place for samples (this is how you import users form a text file or some such thing) the example might be way off, I really just

Re: logging within shell scripts

That appears to be EXACTLY what I'm looking for... Thanx much! On Tue, Sep 14, 1999 at 10:41:10AM +0200, Quant-X UNIX and Linux Support wrote: > Not sure if I understood your question. Anyway, if you want to redirect > a particular file in a shell you don't have to know where it's been > directed

Re: logging within shell scripts

On Mon, Sep 13, 1999 at 08:18:30PM -0500, Gregory T. Norris wrote: > This isn't really a Debian issue as such, but I thought that someone > here might be able to point me in the right direction... Hope I'm not > too far off base here :-) > > I've got a shell script that I want to have log it's act

logging within shell scripts

This isn't really a Debian issue as such, but I thought that someone here might be able to point me in the right direction... Hope I'm not too far off base here :-) I've got a shell script that I want to have log it's actions on a selective basis (dependent upon run-time settings). I know it coul

Re: z/bzImages, shell scripts

rge enough to warrant special code to get it in memory. Also, you don't need to specify /dev/initrd=root.bin, because the kernel will load its root filesystem from /dev/hda2. > > My second question has to do with small shell scripts. I was reading a book > on Unix the other day,

Re: z/bzImages, shell scripts

Tom Lineman <[EMAIL PROTECTED]> writes: TL> My second question has to do with small shell scripts. I was TL> reading a book on Unix the other day, and it talked about TL> "aliases," which it stated only ran under Berkely *nixes. I'm TL> guessing that means FreeB

z/bzImages, shell scripts

ion has to do with small shell scripts. I was reading a book on Unix the other day, and it talked about "aliases," which it stated only ran under Berkely *nixes. I'm guessing that means FreeBSD, NetBSD, OpenBSD, or BSDI, but can Debian linux use aliases, too? The reason I'm a

z/bzImages, shell scripts

/hda2 /dev/initrd=root.bin so that loadlin boots up using the "linux" and "root.bin" files? Or would it be better to use a zImage? My second question has to do with small shell scripts. I was reading a book on Unix the other day, and it talked about "aliases,&qu

Re: Shell scripts

Michael Merten wrote: >Ok, thanks for taking a look at it! (You didn't see anything >obvious that could be done simpler or more efficiently? I always >seem to do things the hard way :) Nothing obvious. -- Vote against SPAM: http://www.politik-digital.de/spam/ ==

Re: Shell scripts

Michael Merten wrote: >On Mon, Aug 09, 1999 at 06:32:26PM +0100, Oliver Elphick wrote: >> Michael Merten wrote: >> >Hi, >> > >> >I've written a rather elaborate shell script and was wondering... >> >are there any script guru's out there with the time and the >> >inclination

Re: Shell scripts

On Mon, Aug 09, 1999 at 07:10:31PM +0200, Jonas Steverud wrote: > Michael Merten <[EMAIL PROTECTED]> writes: > > > I've written a rather elaborate shell script and was wondering... > > are there any script guru's out there with the time and the > > inclination to take a look at it, and possibly gi

Re: Shell scripts

On Mon, Aug 09, 1999 at 11:02:24AM -0500, Michael Merten wrote: > I've written a rather elaborate shell script and was wondering... > are there any script guru's out there with the time and the > inclination to take a look at it, and possibly give me some > suggestions/comments/pointers on how to i

Re: Shell scripts

Michael Merten wrote: >Hi, > >I've written a rather elaborate shell script and was wondering... >are there any script guru's out there with the time and the >inclination to take a look at it, and possibly give me some >suggestions/comments/pointers on how to improve it? I'm happy to lo

Shell scripts

Hi, I've written a rather elaborate shell script and was wondering... are there any script guru's out there with the time and the inclination to take a look at it, and possibly give me some suggestions/comments/pointers on how to improve it? Mike TIA !!! [Private mail welcom

passing ENV var's w/kfm (KDE) launched shell scripts

I thought for a while that I could not launch shell scripts from kfm in my [slink] debian dist. (my slackware dist. works no problem) but it was the environment variables that I was referencing inside the scripts... e.g. below I simply create a kdelnk file using the below script file, and point

Re: shell scripts.

Hello, > of course you're right that Bourne shell has been around for decades, i > guess i wasn't thinking about that one since i really don't know anyone > who uses that as their primary login shell. For quite some time, I used tcsh as login shell and Bourne for scripts... > perhaps it's becaus

Re: shell scripts.

stiions first, > yes perl runs on most every system, but so does the GNU bash shell. can you run it on Vax too? i personally hated programming on VMS, but i was able to do it with Perl. dunno much about compatibility of bash, so i'm just asking. > I tired recompiling my C-programs, so

Re: shell scripts.

piling my C-programs, so I rewrote my simple ones in shell scripts, which I run on both Linux and SunOS/Solaris. As for fading away, the original sh shell has been around for how many decades? (at least 2 decades) Still, perl is often already on other systems without going through a package install

Re: shell scripts.

James Pollard <[EMAIL PROTECTED]> writes: | call me crazy, but after messing around with shell programming for a while, i | discovered perl. i'm no major system programmer or admin or anything, but | why on earth would someone ever want to use some shell programming language | over perl? One wo

Re: shell scripts.

Quoting Jameson Burt ([EMAIL PROTECTED]): > > On Fri, Jan 15, 1999 at 11:37:23PM +1100, Shao Zhang wrote: > > > Hi, > > > Where can I learn how to write the shell scripts?? Is there any > > > good documentation to read?? > > > > > > Thx. &

Re: shell scripts.

I stand corrected. Maybe that is why that program can never be found. ;^) -Original Message- From: Thomas Adams <[EMAIL PROTECTED]> To: debian Date: Saturday, January 16, 1999 2:47 PM Subject: Re: shell scripts. >On Fri, Jan 15, 1999 at 05:52:21AM -0700, Dan Furtney wrote: >

Re: shell scripts.

On Fri, Jan 15, 1999 at 05:52:21AM -0700, Dan Furtney wrote: > scripts. On the back of the book it said shell progamming wasn't covered > because Pearl would be better for the task. I decided to look into Pearl > instead. Good Luck Please don't confuse Pearl with perl. Pearl is a different - if a

Re: shell scripts.

> On Fri, Jan 15, 1999 at 11:37:23PM +1100, Shao Zhang wrote: > > Hi, > > Where can I learn how to write the shell scripts?? Is there any > > good documentation to read?? > > > > Thx. > > > > Shao. > > > > I would recommend O

  1   2   >