From: "Alain M." <alainm@pobox.com>
To: dosEmu-list <linux-msdos@vger.kernel.org>
Subject: Re: Status Update : Deployment of DOSEMU Application Server
Date: Thu, 30 Oct 2008 11:43:52 -0200 [thread overview]
Message-ID: <4909BA18.9010003@pobox.com> (raw)
In-Reply-To: <701247.26345.qm@web52502.mail.re2.yahoo.com>
Ther is only one topic that I can answer:
Shaw Tong Tan escreveu:
>
> 5. One printing downside is CUPS printer do not tolerate long downtime, Example: let say remote client printed some pages in application but failed to put papers in the printer, and nobody care to fix it. After some failed attempts, CUPS daemon noted the problematic status and stop the printer. When remote user later attempt to print again, the printing will have problem because the printer has been stopped on the CUPS side. Admin basically have to access CUPS page to clear jobs and restart the printer. A potential hassle for remote office with a lot of novice users and no onsite IT support, complaining about random failed printing.
Normaly Dosemu (in my setup) sends a print file do a script. This
happens whenever it (dosemu) decides to flush the spool.
So it would be possible to workaround any problem inside this script.
AAMOF, I never have problem with printers out of paper, whenever I
insert paper it starts printing again :)
Alain
next prev parent reply other threads:[~2008-10-30 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 9:02 Status Update : Deployment of DOSEMU Application Server Shaw Tong Tan
2008-10-30 13:42 ` Ivan Baldo
2008-10-30 13:43 ` Alain M. [this message]
2008-10-30 13:45 ` Alain M.
-- strict thread matches above, loose matches on Subject: below --
2008-11-08 16:49 Manfred Scherer
2008-11-09 8:24 ` Claudia Neumann
2008-10-30 17:14 Manfred Scherer
2008-11-02 22:40 ` Claudia Neumann
2008-10-29 5:43 Shaw Tong Tan
2008-10-29 14:33 ` Alain M.
2008-10-29 18:36 ` Andrew Joakimsen
2008-10-29 21:15 ` Alain M.
2008-10-29 21:47 ` Andrew Joakimsen
2008-10-30 1:57 ` Shaw Tong Tan
2008-10-31 0:10 ` Andrew Joakimsen
2008-10-31 2:59 ` Shaw Tong Tan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4909BA18.9010003@pobox.com \
--to=alainm@pobox.com \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox