public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaw Tong Tan <shawtan@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Status Update : Deployment of DOSEMU Application Server
Date: Thu, 30 Oct 2008 02:02:26 -0700 (PDT)	[thread overview]
Message-ID: <701247.26345.qm@web52502.mail.re2.yahoo.com> (raw)

Sorry I was in a hurry in previous post so I now continue with the remaining.

A.  Printing.

1.  PUTTY + REMOTE ANSI Printer + LPANSI was originally preferred since it makes the access and printing very easy for WAN clients.

2.  The plan failed when a client try to print LARGE Print job 32-300Kbytes.  The DOS Application still response but client print queue hung waiting.  Example a 32Kbytes job, it receive approx 4K+ then hung.  I tried various combination sometimes it send close to 8K then hung.

3.  I have 4 variations of lpansi scripts/compiled program for test. Due to the way how I pipe the lpansi program for printing, I also suspect Linux PIPE SIZE setting.  However, to change the setting I need to recompile the kernel, after some thought I gave up the idea.

4.  OPENVPN was eventually chosen so that I can have unrestricted network access between server and WAN clients.  Using CUPS setup, the large print job printed OK.

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.

B.  WAN considerations

1.  Having WAN clients add layers of complication due to the security protection issue.  This is also why I 2nd guessing on opening SSH port facing the Internet.

2.  If support spending is allowed, I would honestly prefer using a vendor-supplied low-cost VPN solution and let the vendor deal with all the complication.  Alternative open solutions (IPCOP/M0N0Wall) available but the VPN reading and related config issues are too numerous for me to address in a short timeframe.  I may revisit them in future.


             reply	other threads:[~2008-10-30  9:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  9:02 Shaw Tong Tan [this message]
2008-10-30 13:42 ` Status Update : Deployment of DOSEMU Application Server Ivan Baldo
2008-10-30 13:43 ` Alain M.
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=701247.26345.qm@web52502.mail.re2.yahoo.com \
    --to=shawtan@yahoo.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