Pedantic indeed! It does, indeed, on unix resolve to
a FILE NAME relative to the local directory named
\IDC-BI2C:TriggersForce_Comment.pl so it's not exactly
a path, per-se, but rather a file name, and most likely
not what the user intended :-)
-Peter
> -----Original Message-----
> From: Lezz Giles [mailto:lgiles@avici.com
> Sent: Thursday, July 19, 2001 4:48 PM
> To: Peter Vogel (QA CCT); 'Raub, Christopher'
> Cc: 'cciug@rational.com'
> Subject: RE: [cciug] Trigger error message (pedantic mode on)
>
>
> I hate to be pedantic, but this is a valid filename on Unix
> filesystems.
> Normally the shell will convert the \\ to a \, and the \C etc
> to C etc,
> but even if you were to pass the filename to open() directly
> it'd still
> be a valid filename. One of my favourite little-known facts about
> Unix is that it is a +lot+ more forgiving about what characters you
> can put into filenames (as far as I know, there are just two that
> you cannot have in a base filename - '/', and NULL) than certain
> other OSs...
>
> Having said that, you're almost certainly right about what's wrong
> with the trigger.
>
> Lezz "not a Unix bigot" Giles
>
>
> At 04:38 PM 07/19/2001 -0700, Peter Vogel (QA CCT) wrote:
>
> >Looks like the trigger is trying to fire a file named
> >ccperl\\IDC-BI2\C:\Tiggers\Force_Comment.pl which is not
> >a valid file name on any system I know of...
> >
> >Perhaps you want the command to be this:
> >
> >ccperl \\IDC-BI2\C\Triggers\Force_Comment.pl ?
> >
> >Note the space between ccperl and the path to the script and
> >the lack of a : after the C since you are using a UNC path, not
> >a local path. Also, since this looks very windows-specific, you may
> >want to use -execwin instead of just plain -exec. Then add a
> -execunix
> >that does the same sort of thing on the unix side (assuming your
> >shop swings both ways :-)
> >
> >-Peter
> >
> > > -----Original Message-----
> > > From: Raub, Christopher [mailto:CRaub@Airbiquity.com
> > > Sent: Thursday, July 19, 2001 4:23 PM
> > > To: 'cciug@rational.com'
> > > Subject: [cciug] Trigger error message
> > >
> > >
> > >
> > > I am getting the following error when I try to make a
> trigger fire.
> > >
> > >
> > >
> > > Error checking in 'U:\CM_practice\HDK\File3.txt'.
> > > Can't exec "ccperl\\IDC-BI2\C:\Triggers\Force_Comment.pl":
> > > The system cannot
> > > find the file specified.
> > > Trigger action "-exec
> > > ccperl\\IDC-BI2\C:\Trigger\Force_Comment.pl" unable to
> > > run: Exec format error
> > >
> > > How do I correct this error?
> > >
> > > As always, thank you.
> > >
> > > Christopher M. Raub
> > > Quality & Configuration Manager
> > > Airbiquity
> > > Direct 206.219.4321
> > > Fax 206.842.9259
> > > www.airbiquity.com
> > >
> > > Contents of this email are confidential
> > >
> > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > >
> > > can also
> > > unsubscribe
> > >
> > > http://clearcase.rational.com/cciug/mailing_list.html
> > >
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >
> > can also
> unsubscribe
> >
> > http://clearcase.rational.com/cciug/mailing_list.html
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:58 EDT