[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: MOSIX for progeny



On Tue, Jun 12, 2001 at 04:17:44AM -0700, christianlavoie@nupedia.com wrote:
> >what I did:
> >root@host# cd /etc/init.d
> >root@host# perl -pi -e 's/start-stop-deamon/mosrun\ -h\ start-stop-deamon/;' *
> >
> >restart whatever you're worried about.
> 
> Problem lies in upgrades. I'm the sysadmin for the machine, but won't be eternally. The lab is a Win2K based one (ugh) and the only few UNIX clueful users will leave before I do. READ: This thing must be apt-upgradable in the long term in the simplest way humanly possible, modifying config files by hand does not fit in that category.
> 
> And, in any way, that's not a 'Good Solution [tm]'.

Yes, I agree with Christian. I believe dpkg-divert can be used to divert
the related conffiles, and there aren't too many that need to be locked.
But, different people would have different views on this.

Another option is to disallow migration as the default. That is, running

mosctl bring && mosctl lstay && mosctl -block && mosctl nomfs

in /etc/init.d/mosix. Probably, /etc/default/mosix can be used to set
the intended defaults, then.

So, a user wanting to allow her processes to migrate would enable process
migration for her shell process, which would allow children to be migrated
out then, or use mosrun etc..

I'm sure various other methods can be used.
If the mosctl method sounds good, I'll put it in.. Let me know..

viral

-- 
"Live for today, gone tomorrow, that's me, HaHaHaaaaaa!"

Attachment: pgpVbI0LcwSFo.pgp
Description: PGP signature


Reply to: