Re: [ptp-dev] Specifying output directory for PTP session

[Greg Watson <g.watson@xxxxxxxxxxxx>]

Ugh. Yes, this needs to be reworked. As I mentioned, I think it should  
now be part of the ConsoleManager (which is a UI function) rather than  
in the model. I'll add it to the TODO list. :-)

Greg

On Nov 27, 2007, at 9:03 AM, Dave Wootton wrote:

> Greg
> Part of the problem seems to be that I have to visit the main PTP
> preferences tab, where the output directory is specified after I  
> create a
> new launch configuration and use that launch configuration.  If I just
> create a new launch configuration and use it without setting  
> preferences
> in the PTP preference panel, then when the setOutputStore method  
> runs, it
> tries to get the value of the PreferenceConstants.OUTPUT_DIR out of  
> the
> preference store, doesn't find it, and sets the path to my  
> workspace. If I
> then view the PTP preferences panel where the output directory is
> specified, click OK, and then run using my launch configuration, it  
> works.
>
> A second problem, which is how I think I discovered this in the first
> place is that the path that is generated for the output file  
> contains the
> proxy name and the queue name as part of the path name. If the proxy  
> name
> contains a '/', that's not detected and invalidated or filtered out.  
> This
> results in a pathname with an extra  directory (because of the '/')  
> and I
> get lots of console messages about an invalid path.
>
> I removed the '/' from my proxy name and now it works.
> Dave
>
>
>
> Greg Watson <g.watson@xxxxxxxxxxxx>
> Sent by: ptp-dev-bounces@xxxxxxxxxxx
> 11/26/2007 03:37 PM
> Please respond to
> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
>
>
> To
> Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
> cc
>
> Subject
> Re: [ptp-dev] Specifying output directory for PTP session
>
>
>
>
>
>
> Dave,
>
> It's supposed to get the path from PreferenceConstants.OUTPUT_DIR,
> which is specified in the PTP preference page. The file creation is
> handled by org.eclipse.ptp.internal.core.elements.PProcess, which
> admittedly is a bit obscure. It should probably by the ConsoleManager
> that handles this now.
>
> Greg
>
> On Nov 26, 2007, at 2:04 PM, Dave Wootton wrote:
>
> > I'm probably missing something, but I don't see anywhere where I can
> > specify the directory that PTP uses for writing stdio output sent  
> > in a
> > process state change event. For some reason, I have one proxy
> > configuration where the output goes to /tmp and everything works
> > fine. I
> > have a second proxy configuration where the output path is a  
> > directory
> > inside the workspace's workspace (.../output) and that fails with
> > messages
> > that the path does not exist for every process change/stdio event.
> >
> > I'm not sure if this makes any difference, but the case that works
> > has the
> > proxy running on the same node as the front end while in the failing
> > case,
> > I'm running the proxy on a different node.
> >
> > Is there somewhere that I'm overlooking where I can set this?
> >
> > Thanks
> > Dave
> > _______________________________________________
> > ptp-dev mailing list
> > ptp-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/ptp-dev
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev