Hi

On 31.08.2016, at 09:37, Marcel Taeumel <marcel.taeumel at hpi.de> wrote:

> " I also discovered I can't apply patches live
> and save the image, because that means its saved with the RFB server
> running."
> 
> That's not good. All patches should be stored in the respective repository and updating the running image, including save, must work. Otherwise some strangely patched monster will grow up and it will be very hard to setup SqueakSource freshly again.

Strange, the last time I used the RFB code, It would always ask me whether to shut down the RFB before saving
just to avoid that.

Also, Why is it bad that the RFB remains running? Isn't that the point?

Best regards
	-Tobias
> 
> Best,
> Marcel
>> Am 31.08.2016 04:47:18 schrieb Chris Muller <ma.chris.m at gmail.com>:
>> 
>> After fixing a bug that let the new server grow to 2.5GB RAM, it is 
>> now stable at 500MB RAM. I also discovered I can't apply patches live 
>> and save the image, because that means its saved with the RFB server 
>> running. 
>> 
>> This large bulk load uncovered a bug when using Magma in direct-mode 
>> since Eliot fixed the process-scheduling to not cycle through 
>> equal-level processes by default -- Magma's flush-to-disk process was 
>> at equal priority and so it wasn't getting flushed! Spur really needs 
>> a way to cap its memory allocation like the old VM's had, so something 
>> like that would not cause problems for other processes on the server.. 
>> 
>> Disk space is so tight, I'll have to log in to delete unneeded commit 
>> log files to avoid us running out. Hopefully Rackspace can afford us 
>> a bigger disk.