RE: scripts

Try altering your modules.conf file, I just had this same issue and that seemed to do the trick. Also becareful if you are using Linuxconf as it may overwrite these settings even though you changed them in the config file, (I had this issue as well).. I think the file is in /etc... If it isnt th

Re: Scripts

On Monday 16 April 2001 12:03, you wrote: -- > > those scripts so I can make up a few 'good' ones that will not only work > > properly but will look pretty.. > > One way around it untill you get a script with start/stop functions is > not to create the Kxx scripts. Then your 3 line script will o

Re: Scripts

On Sun, 15 Apr 2001, Al Sparks wrote: > That's how I've been doing mine. The biggest troubleshooting problem I > had, by the way, is figuring out the path. The "functions" script > located in /etc/rc.d/init.d is where the $PATH is determined at startup > time. > > For example, some of my instal

Re: Scripts

On Mon, 16 Apr 2001, Ted Gervais wrote: > > And I recently discovered chkconfig too so I will be using it if I can ever > make up a few scripts here. I had been just making up a file and putting it > in /etc/rc.d/init.d but it had nothing in it other than 3 lines (give or > take) which was simply

Re: Scripts

On Monday 16 April 2001 03:18, you wrote: > That's how I've been doing mine. The biggest troubleshooting problem I > had, by the way, is figuring out the path. The "functions" script > located in /etc/rc.d/init.d is where the $PATH is determined at startup > time. > > For example, some of my ins

Re: Scripts

That's how I've been doing mine. The biggest troubleshooting problem I had, by the way, is figuring out the path. The "functions" script located in /etc/rc.d/init.d is where the $PATH is determined at startup time. For example, some of my installs placed the binary files in /usr/local/sbin. We

Re: Scripts

-BEGIN PGP SIGNED MESSAGE- Ted Gervais wrote: >But - at some point in time I would certainly like to know how to do this >stuff right, as RedHat would like.. Ted, the fastest way to jump in is to simply copy an existing init script and modify it for your application. They mostly pretty

Re: Scripts

Hi Marco. And hello from NewBrunswick. Well your suggestions are valid and I do appreciate your input. I will try and follow the examples that are there now and if all else fails I will just stick those lines in the /etc/rc.d/rc.local file, as you suggested. I run Slackware here and that is wha

Re: Scripts

> Where does a person go to find out how to make up scripts to install > in /etc/rc.d/init.d so that they run properly. There's no easy way to it that I know of. You just have to look at the existing scripts and build from that. > It seems that just making up a file with only the three lines or

Re: scripts for iptables

http://netfilter.samba.org Mike - Original Message - From: "Barry Schiffman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, April 14, 2001 10:59 AM Subject: scripts for iptables > Does anyone know where there are some sample scripts > for iptables? __

RE: scripts (awk or perl or what?)

I don't recall how to regexprepl all occurences with one pass, but using a script lang like tcl w/sed: ## Repeat using a do while to change from CSV to oeSV: set newdata [exec sed -e s/","/oe/ << $data] ## ##Then: set listdata [split $newdata oe] ## -- To unsubscribe: mail [EMAIL PROTECTED] w

Re: scripts (awk or perl or what?)

On Tue, 18 Jan 2000, Gate wrote: > I need to do the following two things (separately): > > First.. I have a file with comma delineated fields. The data in each field > is enclosed in double quotes ("). However, some data fields have a quote > within the quotes, and I need to remove that. What

Re: scripts (awk or perl or what?)

At 02:40 PM 1/18/00 -0800, Gate wrote: >I need to do the following two things (separately): > >First.. I have a file with comma delineated fields. The data in each field >is enclosed in double quotes ("). However, some data fields have a quote >within the quotes, and I need to remove that. What is

Re: scripts (awk or perl or what?)

Charles, Ouch! You dream bigger than I did. :-) You are correct in that my script doesn't address your example. I'd say that kind of data is "Unintelligable(word?)" and needs to be "Re-CSV'd". Don't get me wrong, I'm not running from it, I just want "Real Data" before investing that kind of time

Re: scripts (awk or perl or what?)

Hi Rick *if* this guys data is really CSV, then by definition, the ',' is the field delimiter. In order to allow ',' characters in the filed data, the data can be enclosed in '"' characters. I don't think they are required though in his data it sounds like all fields are enclosed in '"' chars. An

Re: scripts (awk or perl or what?)

> First.. I have a file with comma delineated fields. The data in each field > is enclosed in double quotes ("). However, some data fields have a quote > within the quotes, and I need to remove that. What is my best choice for > this? As Alan said, this is CSV. If you can tell me how many fields

Re: scripts (awk or perl or what?)

Bryan, Don't listen to those perl guys... ;-) See below On Tue, 18 Jan 2000, Gate wrote: => I need to do the following two things (separately): => => First.. I have a file with comma delineated fields. The data in each field => is enclosed in double quotes ("). However, some data fields have a

Re: scripts no longer work -- ones with arguments?

Paul, Right off hand, I dunno. you might try sh -x /tmp/Configure #(assuming it is a shell script) and see where it dies at. My thoughts, -- Rick L. Mantooth [EMAIL PROTECTED] There are 3 kinds of people: Those who can count and those who can't. On Mon, 17 Jan 2000, Paul R. Watkins wrote

RE: "." appears by default in PATH (was Re: Scripts...)

>Date: Sat, 30 May 1998 17:32:53 -0700 (PDT) >From: Ron Golan <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: "." appears by default in PATH (was Re: Scripts...) > >I'm pretty confused. I tried all your suggestions and even added the echo >lines

Re: xterms don't work after errata (was Re: Scripts...)

In message , Ron Golan writes: >After I sent the message copied below I realized the subject was >misleading and what I think would really help is if someone could tell me >how to capture the error messages when I'm in the Xwindows environment and >

xterms don't work after errata (was Re: Scripts...)

ut go? -- Ron Golan [EMAIL PROTECTED] -- Forwarded message -- Date: Sat, 30 May 1998 23:44:16 -0700 (PDT) From: Ron Golan <[EMAIL PROTECTED]> To: Pete Peterson <[EMAIL PROTECTED]> Cc: Red Hat Linux Mailing List <[EMAIL PROTECTED]> Subject: Re: "." appears by

Re: "." appears by default in PATH (was Re: Scripts...)

After using your good advice to fix that path problem with the errata, I downloaded all the other errata which I thought I might use in the near future. I rpm -Uvh each package. The only one which hasn't worked yet is procps and procps-X11 which need libproc.so.1.2 and libproc.so.1.2.6 respectivel

Re: "." appears by default in PATH (was Re: Scripts...)

> Date: Sat, 30 May 1998 17:32:53 -0700 (PDT) > From: Ron Golan <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: "." appears by default in PATH (was Re: Scripts...) > > I'm pretty confused. I tried all your suggestions an

Re: "." appears by default in PATH (was Re: Scripts...)

At 05:32 PM 5/30/98 -0700, you wrote: Although I really haven't looked too deeply into where the '.' is coming from as it comes from neither the /etc/profile or $HOME/.bash_profile files, I have a very simple solution to remove the '.' edit the /etc/profile file as such: Current PATH statement

Re: "." appears by default in PATH (was Re: Scripts...)

files if this doesn't narrow it down. > [snip] > > > I'd be interested in hearing what you discover. > > > pete peterson > GenRad, Inc. > 7 Technology Park Drive > Westford, MA 01886-0033 > > [EMAIL PROTECT

"." appears by default in PATH (was Re: Scripts...)

589-7478 (GenRad); +1-978-256-5829 (Home: Chelmsford, MA) +1-978-589-2088 (Closest FAX); +1-978-589-7007 (Main GenRad FAX) > Date: Fri, 29 May 1998 21:43:42 -0700 (PDT) > From: Ron Golan <[EMAIL PROTECTED]> > To: Red Hat Linux Mailing List <[EMAIL PROTECTED]> > Subj

Re: Scripts...

[EMAIL PROTECTED] or [EMAIL PROTECTED] > +1-978-589-7478 (GenRad); +1-978-256-5829 (Home: Chelmsford, MA) > +1-978-589-2088 (Closest FAX); +1-978-589-7007 (Main GenRad FAX) > > > > > Date: Fri, 29 May 1998 07:20:49 +0200 (CEST) > > From: Zoki <[EM

Re: Scripts...

(Home: Chelmsford, MA) +1-978-589-2088 (Closest FAX); +1-978-589-7007 (Main GenRad FAX) > Date: Fri, 29 May 1998 07:20:49 +0200 (CEST) > From: Zoki <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: RE: Scripts... > Message-ID: <Pine.LNX.3.96.980529071916.691C-10

RE: Scripts...

Maybe, ls $0 | more Bye -- From: GateKeepeR News[SMTP:[EMAIL PROTECTED]] Sent: Friday, May 29, 1998 5:57 AM To: Zoki Cc: The recipient's address is unknown. Subject: Re: Scripts... Umm, I just tried that and it seemed to work just fine.. On Thu, 28 May 1998,

RE: Scripts...

>What shell are you using? At least in (t)csh, you have either to use the >"rehash" command or to log out and log in again to get the shell to find new >programs. I don't know if bash behaves similar or not, maybe somebode else can >fill in here... :-) IIRC, you only have to rehash under bach whe

Re: Scripts...

Umm, I just tried that and it seemed to work just fine.. On Thu, 28 May 1998, Zoki wrote: |In DOS I use small batch files to express my lazyness and type as few |commands as possible. Super practical. I want to do the same in Linux but |I'm making a thinking mistake somewhere... | |Ex: | S

RE: Scripts...

>Date: Thu, 28 May 1998 17:41:17 +0200 (CEST) >From: Zoki <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: RE: Scripts... >Message-ID: <Pine.LNX.3.96.980528173234.963A-10@localhost> >Content-Type: TEXT/PLAIN; charset=US-ASCII > > >First mistake

Re: Scripts...

Zoki writes: > On Thu, 28 May 1998 [EMAIL PROTECTED] wrote: > ->On Thu, 28 May 1998, Zoki wrote: > -> > ->> First mistake was because of a wrong statement in the script. Next problem > ->> is that it still doesn't work - even with chmod 755 and the dir in the > ->> path - I still have to type ./my

RE: Scripts...

On Thu, 28 May 1998 [EMAIL PROTECTED] wrote: ->On Thu, 28 May 1998, Zoki wrote: -> ->> First mistake was because of a wrong statement in the script. Next problem ->> is that it still doesn't work - even with chmod 755 and the dir in the ->> path - I still have to type ./myscript. Then it works oka

RE: Scripts...

On Thu, 28 May 1998, Zoki wrote: > First mistake was because of a wrong statement in the script. Next problem > is that it still doesn't work - even with chmod 755 and the dir in the > path - I still have to type ./myscript. Then it works okay. What's the > deal on this? Why doesn't it accept t

RE: Scripts...

On Thu, 28 May 1998 [EMAIL PROTECTED] wrote: ->> I found out the equivalent of DOS' "%1" is "$1" in Linux, but "ls ->>$1" doesn't work... -> ->You are correct. What do you mean by "doesn't work"?... Do you have -> -> #!/bin/sh -> ls $1 -> ->Has it a protection mask of 755? (chmod 7

Re: Scripts...

On Thu, 28 May 1998, Dale E Anglin wrote: ->Hi Zoki, -> ->>In DOS I use small batch files to express my lazyness and type as few ->>commands as possible. Super practical. -> ->You might try looking into aliases and shell functions. In basic DOS, one ->is limited to using batch files for this pur

Re: Scripts...

Hi Zoki, >In DOS I use small batch files to express my lazyness and type as few >commands as possible. Super practical. You might try looking into aliases and shell functions. In basic DOS, one is limited to using batch files for this purpose. UNIX system shells usually provide a shorthand or

RE: Scripts...

> I found out the equivalent of DOS' "%1" is "$1" in Linux, but "ls >$1" doesn't work... You are correct. What do you mean by "doesn't work"?... Do you have #!/bin/sh ls $1 Has it a protection mask of 755? (chmod 755 myscript). If it is in the current directory, rather th