SEO

Hi, (sorry for my poor english)

I have to use remote printers from a SCO box.

The network printers are accessible via linux servers (lpd) and are
already in use by other computers (linux via lpd / win via samba), and
so are they well configured and runnable.

Now, i have to configure my SCO box to use those printers from SCO ...
It's a version 3.2, rather old but i can't modify this machine, as
it's a running prod server.

I used "rlpconf" to add the printer in SCO's config. say it's a remote
one, giving it's name, and the name of the computer it's attached to
(so my lpd server)
But printing leads to errors. The file stays in the spool, nothing is
sent to the printer nor the lpd server, but i don't see detailed log
explaining the reason of the failure. Only this when asking lpstat -t
:

printer laser2 waiting for auto-retry. available.
stopped with printer fault

The "configuration" file for the remote printer contains :
Device: laser2@<remoteLinuxBox>
as it was created by "rlpconf". So i guess everything is correct ...

I'm sorry, i'm a linux user, but never used a SCO system before... So
i don't know the good way to do this in the SCO world... It's so easy
with a /etc/printcap file, but i don't have it here !

So if someone could help me, it'd be wonderful ...

Thanks a lot

marc wrote:
> Hi, (sorry for my poor english)
>
> I have to use remote printers from a SCO box.
>
> The network printers are accessible via linux servers (lpd) and are
> already in use by other computers (linux via lpd / win via samba), and
> so are they well configured and runnable.
>
> Now, i have to configure my SCO box to use those printers from SCO ...
> It's a version 3.2, rather old

That's probably the release, not the version number, try uname -v

> but i can't modify this machine, as
> it's a running prod server.
>
> I used "rlpconf" to add the printer in SCO's config. say it's a remote
> one, giving it's name, and the name of the computer it's attached to
> (so my lpd server)

When you configure a "remote unix printer" in OpenServer, the default is
to use SCO's proprietary "extended remote printer protocol" (at least it
is in 'scoadmin printer'). If you have this selected you should deselect it.

> But printing leads to errors.

Such as?

> The file stays in the spool, nothing is
> sent to the printer nor the lpd server, but i don't see detailed log
> explaining the reason of the failure. Only this when asking lpstat -t
> :

What do you have in /etc/printcap?

>
> printer laser2 waiting for auto-retry. available.
> stopped with printer fault
>
> The "configuration" file for the remote printer contains :
> Device: laser2@<remoteLinuxBox>
> as it was created by "rlpconf". So i guess everything is correct ...
>
> I'm sorry, i'm a linux user, but never used a SCO system before... So
> i don't know the good way to do this in the SCO world... It's so easy
> with a /etc/printcap file, but i don't have it here !

Really? All the OSR5 variants I've used will add entries to
/etc/printcap for remote LPD printers.

uname -a?