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

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

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

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 >

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 >

Re: Looping Shell Scripts and System Load

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 whole new set of

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

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

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 >

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

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

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

Looping Shell Scripts and System Load

he 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 working on while all

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

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

On Wed, 17 Jul 2013 06:24:46 +0200, Doug dmcgarr...@optonline.net 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

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 broken English

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 independent of the daytime,

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,

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 the German

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 German.

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. -- To

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. sometimes

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? (although it

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 already

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 below.

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:cdto .profile 3. Modify /etc/passwd: login_dir == /home/user/.rc == example:

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:cdto .profile 3. Modify /etc/passwd: login_dir == /home/user/.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:cdto .profile 3. Modify /etc/passwd: login_dir == /home/user/.rc

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 all

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 raju.mailingli...@gmail.com 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

Re: OT: quoting variable names in shell scripts

On Thu, Jul 7, 2011 at 10:31 AM, Teemu Likonen tliko...@iki.fi wrote: * 2011-07-07T07:13:24+02:00 * Javier Barroso wrote: On Thu, Jul 7, 2011 at 5:22 AM, Kamaraju S Kusumanchi raju.mailingli...@gmail.com wrote: Consider the following shell script #! /bin/sh You can use array variables if

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

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 a r

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

Re: OT: quoting variable names in shell scripts

On Thu, Jul 7, 2011 at 5:22 AM, Kamaraju S Kusumanchi raju.mailingli...@gmail.com 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        

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 association settings

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 x-shellscript

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't usually very useful), just add the x

Rodar shell scripts com poder de root via apache/php

Fala povo! Em busca de uma solução bacana e gerencial para um sistema que utiliza 2 links de internet (não como load balance, e sim como redundancia em caso de queda) estou desenvolvendo uma serie de scripts para trocar de link apenas rodando um script mestre com parametro, ex: host #

Re: Rodar shell scripts com poder de root via apache/php

Acho que o que você quer é o 'sudo'. Rode o script através da interface que o apache lhe proporcione, com o prefixo sudo (como em $ sudo script.sh param1 param2) Configure o sudo para que o usuário do apache possa rodar esse script sem necessidade de senha. Confira no man sudo para isso.

Shell Scripts e Variáveis

Caros, tudo bem ? Estou com uma dúvida de programação de shelll script. Criei um arquivo de configurações como por exemplo arquivo.conf Dentro do arquivo.conf em tenho configurações do tipo campo, exatamente como o httpd.conf e outros. Tipo assim: # Arquivo de configuração de backup e

Re: Shell Scripts e Variáveis

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sérgio Pinheiro wrote: Criei um arquivo de configurações como por exemplo arquivo.conf Dentro do arquivo.conf em tenho configurações do tipo campo, exatamente como o httpd.conf e outros. Tipo assim: # Diretório de Backup dir_backup=/backup

[EMAIL PROTECTED]: kernelpanic curs shell scripts]

-- CURS SHELL-SCRIPTS kernelpanic donar?? un curs de programaci?? del llenguatge de l'int??rpret de comandes bash de GNU/Linux a La Quimera OBJECTIUS: El curs pret??n ser una ajuda per a aquelles persones que, tenint petites nocions de programaci?? i uns coneixements gen

Variables xunges en shell scripts

Doncs be, senyores i senyors, ja he trobat un momentet i he arreglat el problema aquell que vaig comentar no fa gaire sobre les variables recursives en shell scripts Com? Doncs creo un nou fitxer de configuracio temporal pero sense les lines corresponents a les variables que es donen per la linia

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 usable in bash too? Your best option

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 tcsh. I

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 variables?

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. Trouble? Contact [EMAIL

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 you can write anything useful

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 your scripts. Then you will always

Mailing List sur les Shell Scripts ...

Bonjour, Suite aux remarques et aux demandes d'informations concernant les scripts shell, j'ai créé une mailing list dédiée aux shell scripts ... Pour vous abonner, il suffit d'envoyer un mail à : [EMAIL PROTECTED] Puis de répondre au mail qui vous sera envoyé :) Pour vous désabonner

Re: Mailing List sur les Shell Scripts ...

Bonjour, Suite aux remarques et aux demandes d'informations concernant les scripts shell, j'ai créé une mailing list dédiée aux shell scripts ... Tu peux être plus précis sur le sujet de la ML. C'est pour l'échange est la recherche de script tout fait ? Des questions techniques sur comment

RE: Mailing List sur les Shell Scripts ...

[...] Tu peux être plus précis sur le sujet de la ML. C'est pour l'échange est la recherche de script tout fait ? Des questions techniques sur comment programmer en shell ? C'est sur comment organiser l'administration système et simplifier le travail de merde qu'il faut faire régulièrement.

RE: Mailing List sur les Shell Scripts ...

[...] Tiens, c'est drôle, cela fait quelque temps que je lis debian-user-french et du temps où c'était debian-french (avant la séparation -user -devel), il y avait déjà eut une initiative comme celle là, résultat ... une dizaine de messages à tout casser, c'était sur yahoo: [EMAIL PROTECTED] !

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 with

(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: Permission

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 test.sh [EMAIL PROTECTED]:~]$ ./test.sh ./test.sh

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 REALLY evil

Re: (OT) exec nonreadable shell scripts

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 them to a user id that could read the script

Re: (OT) exec nonreadable shell scripts

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, but I've been banging my head trying to set up shell scripts that can be executed

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

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 script

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 would

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! *** [EMAIL PROTECTED]:~]$ chmod 111 test.sh

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 doable. The shell needs to read them

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 feel

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 can be

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 understanding

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

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 script

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

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 don't know

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, I'm anal, and I put

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 have any users, I'm anal, and I

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 of them may be generally useful, so

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 for system or sysadmin or some

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 days a lot of people tend to think

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

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 the

Re: where to put shell scripts?

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 scripts that run under sh can go in /bin or /sbin, if they meet the other criteria, but other interpreted things that have huge runtime systems (like perl scripts

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: 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 users form a text file

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 how you import

Re: complex shell scripts

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) That specific example, no. But I really started cutting my

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

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

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 actions

Re: z/bzImages, shell scripts

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, 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

z/bzImages, shell scripts

/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, which it stated only ran under Berkely

z/bzImages, shell scripts

really appreciate that. One question: would it be possible to use a line somewhat like this: loadlin linux root=/dev/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

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 FreeBSD, NetBSD, OpenBSD, or BSDI, but can TL

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 to take a look at

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/

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

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 look at

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

  1   2   >