Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MQ paths are wrong #122

Open
JorySchossau opened this issue Feb 1, 2018 · 6 comments
Open

MQ paths are wrong #122

JorySchossau opened this issue Feb 1, 2018 · 6 comments

Comments

@JorySchossau
Copy link
Member

when referencing alternative paths, MQ should replace relative paths with absolute paths to the current directory: "../settings.cfg -> settings.cfg" because that's how they are copied.

@JorySchossau
Copy link
Member Author

Conversation w/ Cliff -> Localize MABE dir and no copying would be necessary.

@cliff-bohm
Copy link
Collaborator

cliff-bohm commented Feb 2, 2018 via email

@JorySchossau
Copy link
Member Author

JorySchossau commented Feb 2, 2018 via email

@JorySchossau
Copy link
Member Author

We decided on requiring all files specified must be at or below the same dir level as MABE the MQ call dir. When running on the HPCC the path to each file will be recreated (thus the earlier requirement) and if you need other files outside this requirement, then make it fit the requirement by using symlinks.

@cgnitash
Copy link
Collaborator

So this issue is resolved?

@cgnitash cgnitash added the issue +to be closed Denotes that an issue is probably resolved, so the poster should remove the issue if that's the case label Apr 18, 2018
@JorySchossau
Copy link
Member Author

The folder structure should be recreated on compute nodes for all files specified in MQ by user.

@JorySchossau JorySchossau removed the issue +to be closed Denotes that an issue is probably resolved, so the poster should remove the issue if that's the case label May 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants