I found the following features in burtrb:
usage: burtrb -f req1 {req2 ...} {-l logfile} {-o outfile} {-d} {-v}
{-c ... comments ...} {-k keyword1 ... keywordn}
{-r retry count} {-sdds or -nosdds} {-Dname{=def}}
{-Ipathname}
where
-f req1 {req2 ...} - Request filenames. This is the only switch
that is not optional. You must specify at least one request
file.
Using burtrb from within a directory scecifying just file.req always
crashes burt.
Since I did not believe that we did have some crab in the distribution I used
the burtgooey and had no problems ;-)
Looking at the command beeing executed I saw that the absolute file (including
the directory path) was used. Typing this in:
burtrb -f /dir/dir1/dir2/file.req works!
Well - since not all of us use the gooey ... there's room for improvements.
Matthias
- Navigate by Date:
- Prev:
Re: processing on put to .VAL field Marty Kraimer
- Next:
Re: processing on put to .VAL field Ned Arnold
- Index:
1994
1995
1996
1997
<1998>
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: processing on put to .VAL field William Lupton
- Next:
error in iocLogServer.c Pete Jemian
- Index:
1994
1995
1996
1997
<1998>
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|