On Wed, Jun 13, 2001 at 04:34:55PM -0400, Jonathan D. Proulx wrote: > On Tue, Jun 12, 2001 at 02:34:11PM -0700, christianlavoie@nupedia.com wrote: > :That's indeed a nice idea. Anything installed in daemon space is > :local, anything run from somewhere else isn't. Just a question, how > :do you make daemons migratable? (In case of, say, apache fork()s) > > Hmmm. that is a tangle. > > I did a little testing with nested mosrun's > > "mosrun -h" locks a process to the home node as expected > "mosrun -h mosrun -l" starts it on the home node but allows migration. This doesn't sound too good. That behaviour of mosrun could potentially change in the future.. How about this.. divert /etc/init.d/rc to use a mosix-run script instead of mosrun. This can check /etc/default/mosix, and skip mosrun -h on an init.d script if it has been set to migrate with say: # /etc/default/mosix apache=migrate sshd=stay and those not mentioned would have a default of stay.. > So for a load balancing webserver config you could prepend "mosrun -l" > to the server startup in /etc/init.d/apache. Am I wrong in thinking > that this is a confile and the packagemanagement system won't stomp > changes without asking? Again, its not a good idea modifying files in /etc/init.d.. and to prevent modification of files in /etc/init.d is exactly what we were trying to achieve. This just means that the problem has been simplified now from editing many init.d files to just editing few.. ;-) > So while the rc suggestion doesn't cover all possibilities (I don't > think anything can), it doesn't prevent this level of granularity. -- "There is no dark side of the moon really. Matter of fact it's all dark."
Attachment:
pgpBKFuufZsS_.pgp
Description: PGP signature