You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to allow the configuration of the --output sbatch parameter the same way as for other parameters.
This would enable customisation of the output file as well as passing /dev/null to silent SLURM output.
Alternative options
Leave it as it is: --output={{homedir}}/jupyterhub_slurmspawner_%j.log
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Proposed change
It would be nice to allow the configuration of the
--output
sbatch parameter the same way as for other parameters.This would enable customisation of the output file as well as passing
/dev/null
to silent SLURM output.Alternative options
Leave it as it is:
--output={{homedir}}/jupyterhub_slurmspawner_%j.log
Who would use this feature?
I'm already using a similar feature in jupyterhub_moss, a customized SLURM Spawner (See https://github.com/silx-kit/jupyterhub_moss/blob/fbcf07c7b7198af97e8cd3545458759e5e882b9e/jupyterhub_moss/batch_script.sh#L13), but this requires duplicating the
batch_script
.(Optional): Suggest a solution
Add a
req_output
toSlurmSpawner
(see #258).The text was updated successfully, but these errors were encountered: