[dundee] Scripting across logins

[Bruce Stewart]

Hi Fionnbar,
	Perhaps this is going to sound rather stupid, but as you are printing 
locally to a "PostScript" printer why don't you have the that queue point 
to the print queue on the other machine? So your local queue preprocesses 
to PS then sends the PS document to the remote queue.
As I understand, the queue on the remote machine should process the input 
as if you were sending a document of any format to that queue locally on 
that machine. So if you send a PS document to that queue, it should be 
processed by the remote queue.
Of course this is not printing directly to the lpr/lpd style network port 
on the printer itself (if it has one of course).

Regards
Bruce S.
  
On Saturday 07 Jan 2006 19:00, Fionnbar Lenihan wrote:
> Hi Martin
>
> Thank you very much for the detailed reply
>
> I probably didn't make myself clear.  Printer is recognised fine by
> OS X.  The problem is that the driver which used to work under Jaguar
> 10.3 now doesn't under OS X.4
>
> I would be concerned that if I followed your advice and connected via
> the lpd interface on my iBook I would run into the same driver problem?
>
> My print to PS, copy to remote machine, throw against remote LPR
> method works fine, just very laborious.
>
> Have you any thoughts about expect scripting it?
>
> Would folk have any objections if I posted some of my efforts here?
>
> Cheers
>
> Fionnbar
>
> On 6 Jan 2006, at 11:45, Martin Habets wrote:
> > Hi Fionnbar,
> >
> > On Sun, Jan 01, 2006 at 05:09:05PM +0000, Fionnbar Lenihan wrote:
> >> Hi
> >>
> >> A sort of mixed linux Mac OS X question here.
> >>
> >> When I recently upgraded from OS X 10.3 (Panther) to 10.4 (Tiger) my
> >> Samsung ML-4600 network printer ceased to work despite installing
> >> several drivers.  It's a network printer attached to a simple
> >> Mandrake File / Print server.
> >
> > That's weird. I'd expect the network printer to publish itself using
> > ZeroConf (aka Rendezvous aka Bonjour) and MDNS, which Apple invented.
> > Have you tried running a network sniffer when you tun on the printer?
> > You should look for UDP packets going to port 5353.
> >
> >> I work around it by printing to a Postscript file on a Samba share
> >> located on the  linux server few in my study.  I then SSH into the
> >> server and lpr the PS file
> >>
> >> Works fine and I am pleased with myself though I have a feeling that
> >> I'm somehow re-inventing the wheel!
> >>
> >> I wonder if I can automate this process a  bit?
> >
> > Well, I'd expect all *nix machines to still adhere to the good ol'
> > lpd interface. On your OS X machine have a look at /etc/printcap and
> > put in something like the following:
> >
> > lp|Remote printer entry:\
> >
> >          :lp=:\
> >          :rm=mail.my.domain.net:\
> >          :rp=cx3200:\
> >          :sd=/var/spool/lpd/remote:\
> >          :mx#0:\
> >          :sh:
> >
> > The 'rm' entry hold the name of the print server machine. 'rp' is the
> > queue name on that machine, and 'sd' the directory used on that
> > machine.
> > The first line has the printer name 'lp'.
> >
> > This should be enough to make OS X send the print job to your server
> > machine. On that machine you have to make sure it listens to such
> > requests (which get send using TCP on port 515). I run cups on my
> > print
> > server machine and first added this to /etc/inetd.conf:
> >
> > printer stream  tcp     nowait lp /usr/lib/cups/daemon/cups-lpd
> > cups-lpd
> >
> > Reload your inetd daemon configuration to activate this:
> > /etc/init.d/inetd reload.
> > The other thing I had to do on my server is allow local machines to
> > print. In the security section of /etc/cups/cupsd.conf I have this:
> >
> > <Location />
> > Order Deny,Allow
> > Deny From All
> > Deny from speedtouch
> > Allow From 127.0.0.1
> > Allow From @LOCAL
> > </Location>
> >
> > You won't need the speedtouch line. The speedtouch is my DSL modem.
> > I'm just a bit paranoid in that I don't want anyone from the outside
> > world to have access. Not that the speedtouch is configured to allow
> > this, but as I said I'm just paranoid.
> > Oh yeah, reload the cupsd daemon after updating cupsd.conf.
> >
> > If things don't work, adjust the 'LogLevel' entry in cupsd.conf.
> > And/or send us any errors from lpr and some logs.
> > I use this configuration on my home network. The good thing is that
> > only the server machine has cups and the ppd stuff installed. All the
> > other ones only need lpr.
> >
> > Good luck,
> > --
> > Martin
> > ---------------------------------------------------------------------
> >- -----
> > 30 years from now GNU/Linux will be as redundant a term as MERT/
> > UNIX is
> > today. - Martin Habets
> > ---------------------------------------------------------------------
> >- -----
> >
> > _______________________________________________
> > dundee GNU/Linux Users Group mailing list
> > dundee at lists.lug.org.uk  http://dundee.lug.org.uk
> > http://mailman.lug.org.uk/mailman/listinfo/dundee
> > Chat on IRC, #tlug on dundee.lug.org.uk
>
> _______________________________________________
> dundee GNU/Linux Users Group mailing list
> dundee at lists.lug.org.uk  http://dundee.lug.org.uk
> http://mailman.lug.org.uk/mailman/listinfo/dundee
> Chat on IRC, #tlug on dundee.lug.org.uk