Hello LAM,
I noticed the fellowing behaviour when a LAM session
is initialized with a given priority
[ nice -n 15 lamboot <lamboot_args> ],
the processes running on the original node
herit the priority,
but the processes running on the other nodes
get the normal priority.
This behaviour sounds odd:
it would be nice to allow `lamboot' to propagate
through the cluster its priority.
In such a way the user can easily set a priority
to each LAM_SESSION.
This make sense, since now (LAM 7.0) several LAM sessions can be
initialized (provided different LAM_SESSION_SUFFIX are set).
I hope that helps,
Jerome
|
