Stop incorrect script path from silently failing

Hello,

As a maintainer of the Sigmon analysis notebooks, we rely on our user to pass /eos/project/l/lhcsm/public/packages_notebooks.sh as an environment script when logging into SWAN. However, on multiple occasions, users made a mistake when copy/pasting this environment script, which results in a silent and confusing error.

My proposal would be that, if the provided environment script path doesn’t exist, an error message is displayed and the session is not launched.

Cheers,
Simon

Dear Simon,

Thank you for your feedback :slight_smile:
We will implement this in the future and display an error whenever the environment script path does not exist! You may follow the progress of this task, here: https://its.cern.ch/jira/browse/SWAN-334

Best,
Pedro