[Linux-Discussion] help with /proc/x/lock

  • From: James Gosnell <goose@xxxxxxxxxxxx>
  • To: linux-discussion@xxxxxxxxxxxxx
  • Date: Thu, 07 Jun 2001 12:07:32 -0500

I'm running supercomputing software called MOSIX (I really like it som
far). But to get my processes to migrate to machines of lesser loads
automatically, the /proc/[proc id]/lock file has to be set to '0'. I can
set the bash proc lock file to 0 (echo "0" > /proc/x/lock), then it's
children will be with 0, but does anyone know how I could set all my
processes to a lock of 0 automatically? I would think that having the
init (proc 1) lock set to 0 , everything would be ok and it's children
would be unlocked, but that isn't the case, which I find weird. Is there
a reason that procs are locked? Security issues? ow would I go about
making sure all procs are unlocked automatically at startup? Thank you.
-- 

James Gosnell

__________________________________
Goodwill Industries of Michiana IT
jgosnell@xxxxxxxxxxxxxxx
219-234-1661 x678
=============================================================
Avenir Web's Linux Discussion List

List info: //www.freelists.org/cgi-bin/webpage?webpage_id=13
To unsubscribe: email linux-discussion-request@xxxxxxxxxxxxx
with 'unsubscribe' in the Subject line.

Administrative contact: weez@xxxxxxxxxxxxx
=============================================================

Other related posts:

  • » [Linux-Discussion] help with /proc/x/lock