Re: mosix is in unstable.
>>>>> "v" == viral <viral@debian.org> writes:
v> But, this brings up the point, which services shouldn't be
v> allowed to migrate ? Does mosix by default not allow processes
v> to migrate ? The mosix README suggests using mosrun -h to
v> inittab, for instance.
v> If mosix allows all processes to migrate by default, then maybe
v> in the mosix init scripts, this should be disabled. Then, if
v> one wants processes to migrate, those should be enabled to
v> migrate by hand. What is the right thing to do ?
Probably restrict some of the system processes. Long time ago, when
we first set up our MOSIX cluster to see if it would do the trick for
us, our sysadmin at the time was monitoring migration (mtop on all
cluster machines) in my shared office and started laughing like a
hyena -- turned out that the screensaver on the machine next to him
hopped over to the machine he was monitoring from :-).
The problem is that this requires a small bit of tinkering with
/etc/inetd.conf and /etc/init.d/* if you don't want processes to
unduly migrate (if you let it happen by default). Worse yet,
people run xinetd, too (worse in that it's an option, not in it's
quality).
I think that experience will tell (that, and some real data collection
backed up by the cluster, load, and intent, and we can start fitting
models; but then again, I'm a statistician in my day-job).
--
A.J. Rossini Rsrch. Asst. Prof. of Biostatistics
U. of Washington Biostatistics rossini@u.washington.edu
FHCRC/SCHARP/HIV Vaccine Trials Net rossini@scharp.org
-------- (wednesday/friday is unknown) --------
FHCRC: M-Tu : 206-667-7025 (fax=4812)|Voicemail is pretty sketchy/use Email
UW: Th : 206-543-1044 (fax=3286)|Change last 4 digits of phone to FAX
Reply to: