Is it necessary to restart a sage *server* after installing a spkg ?

[Emmanuel Charpentier]

The documentation points to sage functions allowing to install a new spkg or to upgrade it, whicj explicitely states that such installation is possible.

However, the same doc also states that sage "must be restarted for the changes to take effect.

What is not clear is what happens when you install a new spkg on a *server*. Is it enough to log out of the server and log in again, or should to restart the server process ?

And, oh, by the way : when one starts a server on a Linux machine, PS shows four processes responsible for the server. Is it sufficient to kill -INT the last (topmost) one, or should you always kill all the processes ?

Emmanuel Charpentier

[Keshav Kini]

Emmanuel Charpentier <emanuel.c...@gmail.com> writes:
> The documentation points to sage functions allowing to install a new
> spkg or to upgrade it, whicj explicitely states that such
> installation is possible.
>
> However, the same doc also states that sage "must be restarted for
> the changes to take effect.
>
> What is not clear is what happens when you install a new spkg on a
> *server*. Is it enough to log out of the server and log in again, or
> should to restart the server process ?

It depends on what the SPKG does. If it affects the notebook server at
all, then yes, you would need to restart the notebook server, probably.
If it doesn't affect the notebook server (which is most of the SPKGs),
then you shouldn't need to restart the notebook server itself. You
should restart the Sage worker process that's serving each worksheet,
though. There's a menu option to do this on each worksheet.

-Keshav

[Emmanuel Charpentier]

Thank you very much !

Emmanuel Charpentier