From: C Sights <csights@fa...> - 2003-07-24 12:59:46
> Hi all!
> I'm having problems migrating processes started with "at" command.
> Our users were running process with "at" command, so it runs on a certain
> time of the day. like:
> echo "./program" | at 01:30
> so it runs on a low-utilization time.
> But oM doesn't migrate this processes, and leaves all others 11 nodes wit=
> h 0% utilization, and our "master" node with 100%.
> I would like to know if this is a normal behaviour and if there is a way =
> to run processes with the "at" command and make oM migrate them normally.
I think you want the -l (unlock) mosrun option instead of -h (home).
#echo "mosrun -l ./program" | at midnight
AFAIK all child processes inherit their parent's migratiblity setting unless
a mosrun command is explicitly when starting the child process. So if you
wanted all programs started by atd to migrate then you could start atd with
'mosrun -l /path/to/atd' (in the init scripts somewhere).
From: Cleber Mori <cleber@gr...> - 2003-07-24 16:50:49
On Thu, Jul 24, 2003 at 09:08:33AM -0400, C Sights wrote:
> I think you want the -l (unlock) mosrun option instead of -h (home).
> wanted all programs started by atd to migrate then you could start atd =
> 'mosrun -l /path/to/atd' (in the init scripts somewhere).
Thanks, this solution solved our problems. This way all processes started
with "at" will migrate nicely.=20
I didn't realize that programs started by atd inherited it's migration
properties until you said so. Now it makes sense.
Thank you all again!
Cleber S. Mori
4th Year - Computer Science
ICMC - Mathematics and Computer Science Institute
USP - Sao Paulo University - S=E3o Carlos
Get latest updates about Open Source Projects, Conferences and News.