On Fri, 18 Feb 2011 07:23:35 -0800, Tim wrote:
> When LaTeX encounters a problem it stops processing, asks the user
> what to do (like abort/retry, kind-of), and does whatever the user
> says. The daemon.py script handles that okay from the command line,
> but if I'm understanding you this will be
On Fri, 18 Feb 2011 07:23:35 -0800, Tim wrote:
> Thanks for helping me to understand. I don't know if you're familiar
> with LaTeX, but that's part of what daemon.py calls via subprocess, and
> that is the underlying process I wanted the user to be able to interact
> with.
>
I've used nroff but ne
On Feb 17, 6:09 pm, Martin Gregorie
wrote:
> On Thu, 17 Feb 2011 13:02:08 -0800, Tim wrote:
> > But. The server may encounter a problem
> > during the process and ask the user for more information like
> > 'abort/retry' or something like that.
>
> Servers never ask the client for information: they
On Thu, 17 Feb 2011 13:02:08 -0800, Tim wrote:
> But. The server may encounter a problem
> during the process and ask the user for more information like
> 'abort/retry' or something like that.
>
Servers never ask the client for information: they are strictly request/
response handlers. To do what
On Feb 17, 2:41 pm, Martin Gregorie
wrote:
> On Thu, 17 Feb 2011 08:14:36 -0800, Tim wrote:
> > Hi, I have an inetd service on freebsd that calls a program (daemon.py)
> > with which I want the remote user to communicate. I can call daemon.py
> > from the command line on the host machine and it w
On Feb 17, 2:41 pm, Martin Gregorie
wrote:
> On Thu, 17 Feb 2011 08:14:36 -0800, Tim wrote:
> > Hi, I have an inetd service on freebsd that calls a program (daemon.py)
> > with which I want the remote user to communicate. I can call daemon.py
> > from the command line on the host machine and it w
On Thu, 17 Feb 2011 08:14:36 -0800, Tim wrote:
> Hi, I have an inetd service on freebsd that calls a program (daemon.py)
> with which I want the remote user to communicate. I can call daemon.py
> from the command line on the host machine and it works fine.
>
> What I don't understand is how to m
On Thu, Feb 17, 2011 at 8:14 AM, Tim wrote:
> Hi, I have an inetd service on freebsd that calls a program
> (daemon.py) with which I want the remote user to communicate. I can
> call daemon.py from the command line on the host machine and it works
> fine.
>
> What I don't understand is how to ma
