#381: Sage daemon mode
----------------------------------------------------------+-----------------
Reporter: was | Owner:
mabshoff
Type: enhancement | Status: new
Priority: minor | Milestone:
sage-5.10
Component: user interface | Resolution:
Keywords: Sage server background process service | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
----------------------------------------------------------+-----------------
Comment (by leif):
Replying to [comment:9 jdemeyer]:
> Replying to [comment:8 was]:
> > I think nohup doesn't daemonize.
> True, `nohup` itself doesn't daemonize. But normally you would do
> {{{
> $ nohup sage -n &
> }}}
> It's the `&` at the end which does the "daemonization".
>
> > There is a long list of things that should happen when a process is
damonized:
> >
> > http://en.wikipedia.org/wiki/Daemon_(computing)
> This refers to traditional Unix daemons, which would be quite different
from a Sage "daemon" started by an ordinary user.
>
> So it's not clear to me what would be needed for a Sage daemon which is
not covered by
> {{{
> $ nohup sage &
> }}}
Well, you'd at least also have to `>/dev/null`.
Inherited file descriptors other than 0, 1 and 2 are left untouched.
`nohup` doesn't change the working directory, nor e.g. modify the umask.
The background process doesn't get adopted by `init` until you logout, and
similar process group specific stuff I think.
(...)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/381#comment:12>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
