public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivan Baldo <ibaldo@adinet.com.uy>
To: shawtan@yahoo.com
Cc: linux-msdos@vger.kernel.org
Subject: Re: Status Update : Deployment of DOSEMU Application Server
Date: Thu, 30 Oct 2008 11:42:20 -0200	[thread overview]
Message-ID: <4909B9BC.507@adinet.com.uy> (raw)
In-Reply-To: <701247.26345.qm@web52502.mail.re2.yahoo.com>

  Hello Shaw.
Thanks for sharing your experience!


El 30/10/08 07:02, Shaw Tong Tan escribió:
> 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.
>
>   
There is an option for every printer in the CUPS administration webpage 
that allows to select what to do when print jobs fail, I don't know why 
but the default is "stop-printer", you may change it to "abort-job" or 
"retry-job", that should fix that problem.


> 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.
>
>   
So, you are not comfortable with the VPN setup you made?
Well, maybe you can try FreeNX or NXServer from NoMachine, they are SSH 
based, easy to setup on the clients. I am using FreeNX with printing 
with DOSEmu and OpenOffice, speed is very good.

Hope this helps!!! Bye.

-- 
Ivan Baldo - ibaldo@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: ibaldo@codigolibre.net - http://go.to/ibaldo

--
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-10-30 13:42 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 [this message]
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=4909B9BC.507@adinet.com.uy \
    --to=ibaldo@adinet.com.uy \
    --cc=linux-msdos@vger.kernel.org \
    --cc=shawtan@yahoo.com \
    /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