From: mf j. <mf...@ho...> - 2003-04-19 14:12:56
|
Hello, I have try many things and have not came across a good way to deal with this problem. Therefore, I came here to see what you guys suggest. I'm trying to get all the UML I created to start with main system, but I ran into difficulty because starting an instance of UML would hold the machine at the "Login:" screen. I've tried to get the UML to go into /bin/false and then let the next one boot after that, but that didn't solve it. I'm now considering having to spawn a new "console" and starting the instances of UML from that specific console. All this would be done by the main system rc.local. I haven't found out how specifically to do this. Any help or suggestion would be appreciated. Thanx. Jason _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail |
From: Martin M. <ma...@tw...> - 2003-04-19 16:14:45
|
On Sat, Apr 19, 2003 at 07:12:51AM -0700, mf jp wrote: > I'm trying to get all the UML I created to start with main system, but I ran > into difficulty because starting an instance of UML would hold the machine > at the "Login:" screen. I've tried to get the UML to go into /bin/false and > then let the next one boot after that, but that didn't solve it. I'm now > considering having to spawn a new "console" and starting the instances of > UML from that specific console. All this would be done by the main system > rc.local. I haven't found out how specifically to do this. Any help or > suggestion would be appreciated. Thanx. Jason The problem is that, like most non-daemon programs, UML doesn't disconnect itself from the terminal and background itself. Although it was aimed at slightly different effect of this than your immediate issue, the recent discussion here with the subject "skas mode and networked - solved, one more question" should be helpful. OTOH, if all you want is to get UML off the terminal, and you don't care about losing the boot screen, you could probably just do something like this: linux <other parameters> </dev/null >/dev/null 2>&1 & The redirection disconnects the process from the terminal, and the & backgrounds it so that the shell won't wait. This might be a little more out of the way than is really good - I would at least redirect the output into a per-UML-instance log file. This might also cause a bit more of a thundering herd, since it will go on to start the next UML very quickly. That can be adjusted by a little judicious sleep between startups. Luck! -- To be alive, is that not to be again and again surprised? -- Nicholas van Rijn |
From: Jeff D. <jd...@ka...> - 2003-04-22 20:17:17
|
mf...@ho... said: > I'm trying to get all the UML I created to start with main system, but > I ran into difficulty because starting an instance of UML would hold > the machine at the "Login:" screen. The usual way to do this is to start UML in a detached screen. You get to keep the console output, and the whole thing gets shoved in the background so other things can happen. Jeff |
From: Peter B. <pe...@ra...> - 2003-04-22 23:24:39
|
I'm running several UMLs on a host. FWIW: Each UML runs under a separate user account. And I'm using skas. Occasionally one of the UMLs spikes up to 100% (of the hosts) CPU usage. I've tried renicing those UMLs, but invariably the load on the host increases and other UMLs become less responsive. Ideally, each UML should be able to burst up to the full CPU capability of the host server provided the other UMLs are idle (non-Runnable). However, when more than one UML needs to have CPU, I would like to guarantee it a percentage of the host CPU power, e.g. 1/#umls This is a 'CPU guarantee' is a feature I see promoted on sites hosting on proprietary VPS software (e.g. Virtuozzo). I see there are a couple of host kernel patches out there that may help do this: http://fairsched.sourceforge.net/ http://surriel.com/patches/ Does anyone on the list have experience with these or other similar patches/tools? If so I'd be interested to hear how you got on with them. Regards, Peter |