Skip to content

Shared clusters require .ipython files to be copied to /etc/skel/.ipython/profile_default/startup #7

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

Open
hengrumay opened this issue Apr 7, 2025 · 0 comments

Comments

@hengrumay
Copy link
Collaborator

Test (shared clusters approach) and update documentation from feedback:

On Tue, Jul 9, 2024 at 12:55 PM Eschman, Daniel <[email protected]> wrote:
All,

Thanks again for taking the time to meet yesterday. I was able to get this up and running after a few more modifications. I believe the notebook documenting this sample works only for clusters in single user access mode.

To get it working on my cluster configured for shared access mode, I had to use the init script to copy the python startup script to /etc/skel/.ipython/profile_default/startup This is because the cluster running in shared access mode dynamically creates new users for each session with a random GUID attached to their uid.

By copying the python startup script to a directory under /etc/skel, it ensures that the OS creates those same files in each new user’s $HOME directory and that they are found when the ipython kernel starts for a given notebook.

I was also seeing the same behavior I had previously noted when using a symlink instead of copying the python startup script. The symlink returns an error when a notebook is created that the file does not exist but copying works just fine.

Hopefully that explanation is helpful for building out the documentation a bit further – this trick is big for us!

Best,
Dan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant