Ah sorry, edit /usr/bin/smbprint and change the logfile from /dev/null to
something useful.

On Fri, 16 Jul 1999, Civileme wrote:

> Ummmm,   no error logs.  Everything appears to work fine, but the well is dry
> at the output end.
> 
> If I had error logs, I would likely be reading source code.  I was hoping
> someone could suggest a place to start.
> 
> Civileme
> 
> Axalon wrote:
> 
> > On Fri, 16 Jul 1999, Civileme wrote:
> >
> > > Here is the setup....
> > >
> > > I have a 486 box driving a Winprinter with (what else could it be?)
> > > windows which is on my LAN.
> > >
> > > Mucho many Win95 and Win98 WinWorkboxes print to that printer.  So also
> > > did a lone LinWorkbox running Festen.
> > >
> > > Nothing mysterious.  SMB shared printer.  The Festen box had Samba
> > > configured "All printers /var/spool/lsamba" in the smb.conf file.  The
> > > /etc/printcap entry had \\testrig\hpwin for its target at a static IP
> > > (also identified), and a filter for postscript printers as well as a
> > > target of /var/spool/lpd/lp.  It printed.
> > >
> > > Enter venus.  Venus box, former Festen box now will NOT print.
> > >
> > > Upgrades
> > >
> > > kernel......27
> > > initscripts....26
> > > printtool...5
> > > samba-2.0.4b-8
> > > kdenetwork
> > > net-tools
> > >
> > > Still broken
> > >
> > > Configuration same as what worked with Festen, now, after trying all the
> > > settings combinations I can think of.
> > >
> > > Any advice?  (yeh, get rid of winprinter and use a mini-distribution
> > > with Samba and print facilities on the printbox as I did with the
> > > LaserJet 5Si.)  How can I continue to use the winprinter?  I have
> > > several old boxes and several winprinters to recycle as I move these
> > > folks to the All-Linux office.
> > >
> > > Michael Moore aka Civileme
> > >
> > >
> >
> > I'd need specific error's to trace it, sorry no printers on hand build in
> > this decade.
> 
> --
> Civileme Say:
> 
> "Man who read the fine material available make wiser decisions, much wiser
> after some tinkering and experience."
> 
> 
> 

Reply via email to