This is probably because the Sesame server has a user interface that under Linux is dependent on having an X server still running. When you logged off the Linux box, after starting the server, did you keep your X server running?

As soon as the X server is kaput - so is the Sesame server. The next release (1.0.1) will have a flag on startup that will allow the server to run without a user interface. That will let you set it up as a daemon (you could even put it in rc.d / init.d). In the meantime (it won't be too much longer) keep the X server running, either on the client machine or on the server machine.

Using Hummingbird's Exceed on the client machine as the X server, I was able to telnet into the Linux machine, start Sesame using the PC as the X Server, log off the Linux machine with the X server still running (on the PC) and the Sesame server still displaying on the PC. Sesame was okay until I killed the X Server on the client PC.

Giving the Sesame server an graphical interface was an after-thought based on demand from the Beta testers to have some way to monitor connections. So making it optional should be very easy.