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
General Use Case: user launches funnel and then launches another process to issue the jobs, all while using named sockets to handle communication between the funnel server and the job issuer process. This would allow the job issuer process to use existing file permissions as the socket network by inheriting permissions from the containing directory.
Specific Use Case: user launches funnel on an Exacloud head node with jobs scheduled by Slurm.
This feature should be configurable from the funnel command line:
Overview
General Use Case: user launches funnel and then launches another process to issue the jobs, all while using named sockets to handle communication between the funnel server and the job issuer process. This would allow the job issuer process to use existing file permissions as the socket network by inheriting permissions from the containing directory.
Specific Use Case: user launches funnel on an Exacloud head node with jobs scheduled by Slurm.
This feature should be configurable from the funnel command line:
Funnel server:
Job issuer:
Testing
Minimal testing environment:
Additional Resources
Python Implementation
UNIX Domain Sockets Zine by @jvns
The text was updated successfully, but these errors were encountered: