RE: loginfo parameters

[Chris Cameron]

We use the following line in our shell script to read the standard input
(from memory you can't just read lines in):
BODY=$(cat -)

***************************************************************
Chris Cameron                       Open Telecommunications Ltd
Product Manager                           IN Product Management
address@hidden                           P.O.Box 10-388
      +64 4 495 8403 (DDI)                          The Terrace
fax:  +64 4 495 8419                                 Wellington
cell: +64 21 650 680                                New Zealand
Life, don't talk to me about life ....(Marvin - HHGTTG)

> -----Original Message-----
> From: address@hidden [mailto:address@hidden Behalf Of
> CORUM, M E [AG/1000]
> Sent: Thursday, 16 August 2001 11:34 a.m.
> To: 'Jennifer Hamilton '; CORUM, M E [AG/1000]; 'address@hidden '
> Subject: RE: loginfo parameters
>
>

snip

> The loginfo doc says that my script should expect something on
> standard input.  If I do a read in my Bourne shell script, I get an
> error about a broken pipe (meaning standard input had nothing) and
> nothing is read into the variable.  It would be great if the commit
> output I see on the screen would be sent into my shell script somehow
> because the file name has the critical last slash in the directory
> hierarchy before the file name itself.  Should I not be using the
> read statement?  I don't know.  Thanks for replying.
>
> Mike
>
> -----Original Message-----
> From: Jennifer Hamilton
> To: CORUM, M E [AG/1000]; address@hidden
> Sent: 8/15/01 6:17 PM
> Subject: RE: loginfo parameters
>
> If loginfo is a shell script, perhaps you use the escape character "\"
> to show that the space should be used literally.
>
> example,
> /project/docs/use\ cases/my\ use\ case.doc
>
> Jen
>
> -----Original Message-----
> From: CORUM, M E [AG/1000] [mailto:address@hidden
> Sent: Wednesday, August 15, 2001 3:46 PM
> To: 'address@hidden'
> Subject: loginfo parameters
>
>
>
> I'm trying to use loginfo to run a script that exports a file out and
> then copies it somewhere.  The problem is that the project team must
> use spaces in its directories and file names.  When the parameter for
> the file name (%s) comes into the script, the last slash is removed and
> only a single space separates the directory from the file name.  If
> both the directory and file name have spaces, there is no way to tell
> where the directory ends and the file name begins:
>
> /project/docs/use cases/my use case.doc
>
> gets handed into the loginfo script as:
>
> /project/docs/use cases my use case.doc
>
> Can anybody help here?  Is there some secret way to have it just hand
> in the directory in a parm?  I can't hard-code the directories into
> the loginfo file because they will be adding new directories hourly
> and I wouldn't be able to keep up with their requirements for adding
> new lines into the loginfo script.  The online version of the Fogel
> book implies that there are two spaces between the directory and the
> list of files but that is not the case in 1.10.
>
> Any help would be appreciated.
>
> Mike
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>