Perhaps because of my Windows 'up-bringing', I'm a firm beleiver of 'rebooting often'. Hopefully, I can leave the Linux server running more often, but I do see a need to reboot every few days, at least.

My biggest reason; After loading,unloading, and designing my largest aps, The sesame Terminal windows shows this error message: "Warning! File buffer allocation is greater than half of available memory."

At this point, I observe loading times slow down dramatically (perhaps the memory is swapping). Rebooting the machine has always fixed this issue.

So, my concern; after using the '-command' option, I can no longer get a graceful shutdown when I use 'stop this server' option from within the admin panel.

Perhaps there is a better method for shutting down the server?

Steve

You should almost never reboot a Unix box. I have had boxes that have up-times measured in years. It is much better about memory management than Windows.

The loading message is caused by the new application loader. Instead of reading the file in a bit at a time, it reads the whole file in one big chunk and then parses that out to the final in memory structure and deallocates the big chunk. So, temporarily it needs twice as much memory. If there is not enough memory, it will revert to the older load. That message means that it will use the older load, which should only affect the speed of loading applications, not general run speed.

You should not reboot your server computer because you are backing up Sesame files. In general, on Unix, the only reason to shutdown the box is when you get a kernel update, the room is on fire, or you simply want to save electricity.

You can shutdown Sesame using the same command interface you are using to suspend and resume.

Hello Steve,

I also just tried this on my Linux box and am unable to reproduce the clients stacking up in the admin panel. Can you send me your Sesame.ini file in case there is something in there that I need?

-Ray