OS: Openserver 5.0.5
Task: add a remote printer via rlpconf or scoadmin
What should happen: printer queue should show up in output of lpstat
-t
What's happening instead: proper entries are created in /etc/printcap,
var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
run lpstat -t the printer does not show up.
---output of lpstat -t-----
scheduler is running
no system default destination
device for s093ptr002: /dev/lp0
device for s093ptr003: s093ptr003@s093ptr003
s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
available.
---end----
When I attempt to start scoadmin printer, I'm getting this in /var/
adm/syslog
----tail of syslog-----
Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
{s093ptr003} err
or SCO_OFACE_MSG_ERROR {error
{{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
eral failure occurred in processing attribute printerDescription}}
{SCO_NONSTD_C
MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
TO FIX: Use the "lpstat -p all" command to list all known
printers}}}}
I had to delete a badly configured queue with the same name
(s093ptr003) before attempting to create this one. I used the
scoadmin printer tool to delete the old queue. I've also found that
if I manually delete the entries in printcap, lpd and lp/printers,
scoadmin will start just fine. Ideas?
Thanks in advance.
Dave
|
|
0
|
|
|
|
Reply
|
 dthacker
|
2/9/2011 3:57:05 PM |
|
This is a multi-part message in MIME format.
--------------040008070109040503040405
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
dthacker wrote:
> OS: Openserver 5.0.5
> Task: add a remote printer via rlpconf or scoadmin
> What should happen: printer queue should show up in output of lpstat
> -t
> What's happening instead: proper entries are created in /etc/printcap,
> var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
> run lpstat -t the printer does not show up.
> ---output of lpstat -t-----
> scheduler is running
> no system default destination
> device for s093ptr002: /dev/lp0
> device for s093ptr003: s093ptr003@s093ptr003
> s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
> printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
> available.
> ---end----
>
> When I attempt to start scoadmin printer, I'm getting this in /var/
> adm/syslog
> ----tail of syslog-----
> Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
> {s093ptr003} err
> or SCO_OFACE_MSG_ERROR {error
> {{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
> eral failure occurred in processing attribute printerDescription}}
> {SCO_NONSTD_C
> MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
> TO FIX: Use the "lpstat -p all" command to list all known
> printers}}}}
>
> I had to delete a badly configured queue with the same name
> (s093ptr003) before attempting to create this one. I used the
> scoadmin printer tool to delete the old queue. I've also found that
> if I manually delete the entries in printcap, lpd and lp/printers,
> scoadmin will start just fine. Ideas?
>
> Thanks in advance.
>
> Dave
>
>
>
Dave,
I have always felt that the SCO rlp was a poor choice. See this post on
using rlpr: *http://preview.tinyurl.com/6dwq49e*
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
--------------040008070109040503040405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
dthacker wrote:
<blockquote
cite="mida2ebf420-8a06-4e77-a069-82b15c8a8629@i40g2000yqh.googlegroups.com"
type="cite">
<pre wrap="">OS: Openserver 5.0.5
Task: add a remote printer via rlpconf or scoadmin
What should happen: printer queue should show up in output of lpstat
-t
What's happening instead: proper entries are created in /etc/printcap,
var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
run lpstat -t the printer does not show up.
---output of lpstat -t-----
scheduler is running
no system default destination
device for s093ptr002: /dev/lp0
device for s093ptr003: s093ptr003@s093ptr003
s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
available.
---end----
When I attempt to start scoadmin printer, I'm getting this in /var/
adm/syslog
----tail of syslog-----
Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
{s093ptr003} err
or SCO_OFACE_MSG_ERROR {error
{{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
eral failure occurred in processing attribute printerDescription}}
{SCO_NONSTD_C
MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
TO FIX: Use the "lpstat -p all" command to list all known
printers}}}}
I had to delete a badly configured queue with the same name
(s093ptr003) before attempting to create this one. I used the
scoadmin printer tool to delete the old queue. I've also found that
if I manually delete the entries in printcap, lpd and lp/printers,
scoadmin will start just fine. Ideas?
Thanks in advance.
Dave
</pre>
</blockquote>
Dave, <br>
<br>
I have always felt that the SCO rlp was a poor choice. See this post on
using rlpr: <b><a class="moz-txt-link-freetext" href="http://preview.tinyurl.com/6dwq49e">http://preview.tinyurl.com/6dwq49e</a></b><br>
<pre class="moz-signature" cols="360">--
Steve Fabac
S.M. Fabac & Associates
816/765-1670</pre>
</body>
</html>
--------------040008070109040503040405--
|
|
|
0
|
|
|
|
Reply
|
Steve
|
2/9/2011 5:41:24 PM
|
|
dthacker wrote:
> OS: Openserver 5.0.5
> Task: add a remote printer via rlpconf or scoadmin
> What should happen: printer queue should show up in output of lpstat
> -t
> What's happening instead: proper entries are created in /etc/printcap,
> var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
> run lpstat -t the printer does not show up.
> ---output of lpstat -t-----
> scheduler is running
> no system default destination
> device for s093ptr002: /dev/lp0
> device for s093ptr003: s093ptr003@s093ptr003
> s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
> printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
> available.
> ---end----
>
> When I attempt to start scoadmin printer, I'm getting this in /var/
> adm/syslog
> ----tail of syslog-----
> Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
> {s093ptr003} err
> or SCO_OFACE_MSG_ERROR {error
> {{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
> eral failure occurred in processing attribute printerDescription}}
> {SCO_NONSTD_C
> MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
> TO FIX: Use the "lpstat -p all" command to list all known
> printers}}}}
>
> I had to delete a badly configured queue with the same name
> (s093ptr003) before attempting to create this one. I used the
> scoadmin printer tool to delete the old queue. I've also found that
> if I manually delete the entries in printcap, lpd and lp/printers,
> scoadmin will start just fine. Ideas?
>
> Thanks in advance.
>
> Dave
>
>
Dave,
I have always felt that the SCO rlp was a poor choice. See this
post on using rlpr: http://preview.tinyurl.com/6dwq49e
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
|
|
|
0
|
|
|
|
Reply
|
Steve
|
2/9/2011 11:52:08 PM
|
|
On Feb 9, 5:52=A0pm, "Steve M. Fabac, Jr." <smfa...@att.net> wrote:
> dthacker wrote:
> > OS: =A0Openserver 5.0.5
> > Task: =A0 add a remote printer via rlpconf or scoadmin
> > What should happen: =A0 printer queue should show up in output of lpsta=
t
> > -t
> > What's happening instead: proper entries are created in /etc/printcap,
> > var/spool/lpd and /var/spool/lp/admins/lp/printers. =A0 However when I
> > run lpstat -t the printer does not show up.
> > ---output of lpstat -t-----
> > scheduler is running
> > no system default destination
> > device for s093ptr002: /dev/lp0
> > device for s093ptr003: s093ptr003@s093ptr003
> > s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
> > printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
> > available.
> > ---end----
>
> > =A0When I attempt to start scoadmin printer, I'm getting this in /var/
> > adm/syslog
> > ----tail of syslog-----
> > Feb =A09 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
> > {s093ptr003} err
> > or SCO_OFACE_MSG_ERROR {error
> > {{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
> > eral failure occurred in processing attribute printerDescription}}
> > {SCO_NONSTD_C
> > MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
> > =A0TO FIX: Use the "lpstat -p all" command to list all known
> > printers}}}}
>
> > I had to delete a badly configured queue with the same name
> > (s093ptr003) before attempting to create this one. =A0 I used the
> > scoadmin printer tool to delete the old queue. =A0 I've also found that
> > if I manually delete the entries in printcap, lpd and lp/printers,
> > scoadmin will start just fine. =A0 Ideas?
>
> > Thanks in advance.
>
> > Dave
>
> Dave,
>
> I have always felt that the SCO rlp was a poor choice. See this
> post on using rlpr:http://preview.tinyurl.com/6dwq49e
>
Steve
rlpr looks interesting, but I'm not sure can take 140 servers down
that road right now. In the meantime, I'm still looking for a
configuration file for scoadmin printers that might explain the error
message I'm receiving.
TIA
Dave
|
|
|
0
|
|
|
|
Reply
|
dthacker
|
2/28/2011 9:22:26 PM
|
|
On 2/28/2011 1:22 PM, dthacker wrote:
> On Feb 9, 5:52 pm, "Steve M. Fabac, Jr."<smfa...@att.net> wrote:
>> dthacker wrote:
>>> OS: Openserver 5.0.5
>>> Task: add a remote printer via rlpconf or scoadmin
>>> What should happen: printer queue should show up in output of lpstat
>>> -t
>>> What's happening instead: proper entries are created in /etc/printcap,
>>> var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
>>> run lpstat -t the printer does not show up.
>>> ---output of lpstat -t-----
>>> scheduler is running
>>> no system default destination
>>> device for s093ptr002: /dev/lp0
>>> device for s093ptr003: s093ptr003@s093ptr003
>>> s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
>>> printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
>>> available.
>>> ---end----
>>
>>> When I attempt to start scoadmin printer, I'm getting this in /var/
>>> adm/syslog
>>> ----tail of syslog-----
>>> Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
>>> {s093ptr003} err
>>> or SCO_OFACE_MSG_ERROR {error
>>> {{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
>>> eral failure occurred in processing attribute printerDescription}}
>>> {SCO_NONSTD_C
>>> MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
>>> TO FIX: Use the "lpstat -p all" command to list all known
>>> printers}}}}
>>
>>> I had to delete a badly configured queue with the same name
>>> (s093ptr003) before attempting to create this one. I used the
>>> scoadmin printer tool to delete the old queue. I've also found that
>>> if I manually delete the entries in printcap, lpd and lp/printers,
>>> scoadmin will start just fine. Ideas?
>>
>>> Thanks in advance.
>>
>>> Dave
>>
>> Dave,
>>
>> I have always felt that the SCO rlp was a poor choice. See this
>> post on using rlpr:http://preview.tinyurl.com/6dwq49e
>>
> Steve
>
> rlpr looks interesting, but I'm not sure can take 140 servers down
> that road right now. In the meantime, I'm still looking for a
> configuration file for scoadmin printers that might explain the error
> message I'm receiving.
>
> TIA
>
> Dave
>
>
This may be simplistic, but how about just renaming the printer and
documenting that that old name is not to be used in the future?
Or try grep'ing through the entire /usr/spool, /var/spool hierarchy for
the name?
Have you manually emptied and deleted the spooler control files and the
data files associated with the printer?
--
----------------------------------------------------
Pat Welch, UBB Computer Services, a WCS Affiliate
SCO Authorized Partner
Microlite BackupEdge Certified Reseller
Unix/Linux/Windows/Hardware Sales/Support
(209) 745-1401 Cell: (209) 251-9120
E-mail: patubb@inreach.com
----------------------------------------------------
|
|
|
0
|
|
|
|
Reply
|
Pat
|
3/1/2011 1:04:38 AM
|
|
This is a multi-part message in MIME format.
--------------070104090709070903010300
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
dthacker wrote:
> On Feb 9, 5:52 pm, "Steve M. Fabac, Jr." <smfa...@att.net> wrote:
>
>> dthacker wrote:
>>
>>> OS: Openserver 5.0.5
>>> Task: add a remote printer via rlpconf or scoadmin
>>> What should happen: printer queue should show up in output of lpstat
>>> -t
>>> What's happening instead: proper entries are created in /etc/printcap,
>>> var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
>>> run lpstat -t the printer does not show up.
>>> ---output of lpstat -t-----
>>> scheduler is running
>>> no system default destination
>>> device for s093ptr002: /dev/lp0
>>> device for s093ptr003: s093ptr003@s093ptr003
>>> s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
>>> printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
>>> available.
>>> ---end----
>>>
>>> When I attempt to start scoadmin printer, I'm getting this in /var/
>>> adm/syslog
>>> ----tail of syslog-----
>>> Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
>>> {s093ptr003} err
>>> or SCO_OFACE_MSG_ERROR {error
>>> {{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
>>> eral failure occurred in processing attribute printerDescription}}
>>> {SCO_NONSTD_C
>>> MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
>>> TO FIX: Use the "lpstat -p all" command to list all known
>>> printers}}}}
>>>
>>> I had to delete a badly configured queue with the same name
>>> (s093ptr003) before attempting to create this one. I used the
>>> scoadmin printer tool to delete the old queue. I've also found that
>>> if I manually delete the entries in printcap, lpd and lp/printers,
>>> scoadmin will start just fine. Ideas?
>>>
>>> Thanks in advance.
>>>
>>> Dave
>>>
>> Dave,
>>
>> I have always felt that the SCO rlp was a poor choice. See this
>> post on using rlpr:http://preview.tinyurl.com/6dwq49e
>>
>>
> Steve
>
> rlpr looks interesting, but I'm not sure can take 140 servers down
> that road right now. In the meantime, I'm still looking for a
> configuration file for scoadmin printers that might explain the error
> message I'm receiving.
>
> TIA
>
> Dave
>
>
>
>
Dave,
You have the same printer problem on 140 servers? or just one? Change
the one with the problem and you will wonder why you waited. I know that
I resisted using netcat for the longest time and after I converted on
system I became a true believer and apostle.
On a customer's SCO 5.0.5 system after I installed OSS646C (April
2008), the customer complained that the system was real slow and would
not shut down and reboot. When I logged in and checked there were
repeated messages in syslog:
"unix lpd[9999] unknown printer: (BSD format)" repeated over and over
10-20 times per second and inflated syslog to over 240Mb..
Removing OSS646C stopped the error message. Searching on the problem
revealed OSS663a the lpd daemon patch (specific to 5.0.6) that installed
after OSS646C was reinstalled and that fixed the problem of unknown
printer messages logged to syslog.
> Dear SCO Customer,
>
> Support Level Supplement (SLS) OSS663A, the LPD supplement for
> OpenServer 5.0.6 with OSS646, addresses a problem that
> occurs when either OSS646a or OSS646b is installed on an
> OpenServer 5.0.6 system with lpd printers defined.
>
> With OSS646 installed, lpd has a problem parsing
> /etc/printcap that results in a lot of entries in the
> syslog about unknown printer, similar to this:
>
> Jul 24 15:16:27 scosysv lpd[9160]: unknown printer: 026
Maybe your problem is related to OSS646C recently installed?
What I dislike with SCO's rlp is that lpstat -t has to go out to each
printer host and ask for the printer's status. One printer, no problem.
40 printers forget it. Also the problems with lpstat with rlp broke my
printer administration menu:
PRINTER=laser
PRINTER CONTROL MENU FOR smf
1) ENABLE A PRINTER
2) DISABLE A PRINTER
3) CHANGE PRINTERS
4) KILL A PRINT REQUEST
5) MOVE PRINT REQUESTS FROM
ONE PRINTER TO ANOTHER
6) PRINTER STATUS
7) RESTART PRINTERS
8) KILL ALL JOBS ON SPECIFIED PRINTER
X) EXIT
PLEASE SELECT (or 'H' for HELP):
Nearly all of the above choices rely on using output of lpstat -p to get
a working list of printers and jobs. The hang-up of a single rlp host
prevents the scripts from running as designed.
# PRINTER CONTROL MENU
# @(#) LPCMENU 1.6 9/6/96"
#
lplist() {
lpstat -p | awk '{ printf "%-14s", $2
for (i = 2; i <= NF; i++ ) {
if ( $i == "enabled" )
printf "%8s\n", $i
if ( $i == "disabled") {
printf "%8s:", $i
getline
printf "%s\n", $0 } } } ';
}
prtpth=/usr/spool/lp/admins/lp/interfaces
trap '' 2
while(true)
do
tput clear
tput smso
echo "
PRINTER=$LPDEST
tput cuu1
echo " PRINTER CONTROL MENU FOR
$USER
tput rmso
cat <<!
....
2)
tput clear;
echo "LIST OF PRINTERS......";
echo "===============================";
lplist
# echo "";
echo "===============================";
echo "SELECT PRINTER TO DISABLE : ";
read pra;
if [ `lpstat -p $pra | awk ' { print $2 } ' | grep
"${pra:-null}$" ` ]
then
echo "Enter a Reason for disabling " $pra "-c"
read reason
disable -r"${reason}" $pra;
elif test -n "$pra"
then
echo "PRINTER "$pra" DOES NOT EXIST Press <ENTER> to Return to
Menu";
read pra;
fi
echo;;
....
8)
tput clear
echo " THE FOLLOWING IS A LIST OF ACTIVE PRINT REQUESTS..... ";
echo "======================================================";
lpstat -u
echo "======================================================";
echo "SELECT PRINTER TO CANCLE : \c"
read pra
[ `lpstat -p | awk ' { print $2 } ' | grep "${pra:-null}$" ` ] && {
cnt=0
for i in `lpstat $pra | awk '{ print $1 }' `
do
cnt=`expr $cnt + 1`
cancel $i
done
[ $cnt -eq "0" ] && {
echo
echo "JOBS for PRINTER "$pra" DO NOT EXIST Press <ENTER>
to Retu
} || {
echo
true
echo "Press <ENTER> to return to Menu"
true
}
read me
} || {
[ -n "$pra" ] && {
echo;echo "PRINTER "$pra" DOES NOT EXIST Press <ENTER> to
Return t
read me
}
}
;;
X|x)
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
--------------070104090709070903010300
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
dthacker wrote:
<blockquote
cite="mid21442bd4-2b84-47d2-9182-e61c2f109468@w7g2000pre.googlegroups.com"
type="cite">
<pre wrap="">On Feb 9, 5:52 pm, "Steve M. Fabac, Jr." <a class="moz-txt-link-rfc2396E" href="mailto:smfa...@att.net"><smfa...@att.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">dthacker wrote:
</pre>
<blockquote type="cite">
<pre wrap="">OS: Openserver 5.0.5
Task: add a remote printer via rlpconf or scoadmin
What should happen: printer queue should show up in output of lpstat
-t
What's happening instead: proper entries are created in /etc/printcap,
var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
run lpstat -t the printer does not show up.
---output of lpstat -t-----
scheduler is running
no system default destination
device for s093ptr002: /dev/lp0
device for s093ptr003: s093ptr003@s093ptr003
s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
available.
---end----
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap=""> When I attempt to start scoadmin printer, I'm getting this in /var/
adm/syslog
----tail of syslog-----
Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
{s093ptr003} err
or SCO_OFACE_MSG_ERROR {error
{{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
eral failure occurred in processing attribute printerDescription}}
{SCO_NONSTD_C
MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
TO FIX: Use the "lpstat -p all" command to list all known
printers}}}}
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">I had to delete a badly configured queue with the same name
(s093ptr003) before attempting to create this one. I used the
scoadmin printer tool to delete the old queue. I've also found that
if I manually delete the entries in printcap, lpd and lp/printers,
scoadmin will start just fine. Ideas?
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">Thanks in advance.
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">Dave
</pre>
</blockquote>
<pre wrap="">Dave,
I have always felt that the SCO rlp was a poor choice. See this
post on using rlpr:<a class="moz-txt-link-freetext" href="http://preview.tinyurl.com/6dwq49e">http://preview.tinyurl.com/6dwq49e</a>
</pre>
</blockquote>
<pre wrap=""><!---->Steve
rlpr looks interesting, but I'm not sure can take 140 servers down
that road right now. In the meantime, I'm still looking for a
configuration file for scoadmin printers that might explain the error
message I'm receiving.
TIA
Dave
</pre>
</blockquote>
Dave,<br>
<br>
You have the same printer problem on 140 servers? or just one? Change
the one with the problem and you will wonder why you waited. I know
that I resisted using netcat for the longest time and after I converted
on system I became a true believer and apostle.<br>
<br>
On a customer's SCO 5.0.5 system after I installed OSS646C (April
2008), the customer complained that the system was real slow and would
not shut down and reboot. When I logged in and checked there were
repeated messages in syslog: <br>
<br>
"unix lpd[9999] unknown printer: (BSD format)" repeated over and over
10-20 times per second and inflated syslog to over 240Mb..<br>
<br>
Removing OSS646C stopped the error message. Searching on the problem
revealed OSS663a the lpd daemon patch (specific to 5.0.6) that
installed after OSS646C was reinstalled and that fixed the problem of
unknown printer messages logged to syslog. <br>
<br>
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span"
style="font-family: 'Courier New',Arial,Helvetica,Tahoma,sans-serif; font-size: 13px;">
<pre> Dear SCO Customer,
Support Level Supplement (SLS) OSS663A, the LPD supplement for
OpenServer 5.0.6 with OSS646, addresses a problem that
occurs when either OSS646a or OSS646b is installed on an
OpenServer 5.0.6 system with lpd printers defined.
With OSS646 installed, lpd has a problem parsing
/etc/printcap that results in a lot of entries in the
syslog about unknown printer, similar to this:
Jul 24 15:16:27 scosysv lpd[9160]: unknown printer: 026 </pre>
</span></span></blockquote>
<br>
<br>
Maybe your problem is related to OSS646C recently installed? <br>
<br>
What I dislike with SCO's rlp is that lpstat -t has to go out to each
printer host and ask for the printer's status. One printer, no problem.
40 printers forget it. Also the problems with lpstat with rlp broke my
printer administration menu:<br>
<br>
<tt>
PRINTER=laser <br>
PRINTER CONTROL MENU FOR smf
<br>
<br>
<br>
1) ENABLE A PRINTER<br>
<br>
2) DISABLE A PRINTER<br>
<br>
3) CHANGE PRINTERS<br>
<br>
4) KILL A PRINT REQUEST<br>
<br>
5) MOVE PRINT REQUESTS FROM<br>
ONE PRINTER TO ANOTHER<br>
<br>
6) PRINTER STATUS<br>
<br>
7) RESTART PRINTERS<br>
<br>
8) KILL ALL JOBS ON SPECIFIED PRINTER<br>
<br>
X) EXIT<br>
PLEASE SELECT (or 'H' for HELP): <br>
<br>
Nearly all of the above choices rely on using output of lpstat -p to
get a working list of printers and jobs. The hang-up of a single rlp
host prevents the scripts from running as designed.<br>
<br>
# PRINTER CONTROL MENU<br>
# @(#) LPCMENU 1.6 9/6/96"<br>
#<br>
lplist() {<br>
lpstat -p | awk '{ printf "%-14s", $2<br>
for (i = 2; i <= NF; i++ ) {<br>
if ( $i == "enabled" )<br>
printf "%8s\n", $i <br>
if ( $i == "disabled") {<br>
printf "%8s:", $i<br>
getline<br>
printf "%s\n", $0 } } } ';<br>
}<br>
prtpth=/usr/spool/lp/admins/lp/interfaces<br>
trap '' 2<br>
while(true)<br>
do<br>
tput clear<br>
tput smso<br>
echo "
PRINTER=$LPDEST <br>
tput cuu1<br>
echo " PRINTER CONTROL MENU FOR
$USER <br>
tput rmso<br>
cat <<!<br>
....<br>
2)<br>
tput clear;<br>
echo "LIST OF PRINTERS......";<br>
echo "===============================";<br>
lplist<br>
# echo "";<br>
echo "===============================";<br>
echo "SELECT PRINTER TO DISABLE : ";<br>
read pra;<br>
if [ `lpstat -p $pra | awk ' { print $2 } ' | grep
"${pra:-null}$" ` ] <br>
then<br>
echo "Enter a Reason for disabling " $pra "-c"<br>
read reason<br>
disable -r"${reason}" $pra;<br>
elif test -n "$pra"<br>
then<br>
echo "PRINTER "$pra" DOES NOT EXIST Press <ENTER> to
Return to Menu";<br>
read pra;<br>
fi<br>
echo;;<br>
....<br>
8)<br>
tput clear<br>
echo " THE FOLLOWING IS A LIST OF ACTIVE PRINT REQUESTS..... ";<br>
echo "======================================================";<br>
lpstat -u<br>
echo "======================================================";<br>
echo "SELECT PRINTER TO CANCLE : \c"<br>
read pra<br>
[ `lpstat -p | awk ' { print $2 } ' | grep "${pra:-null}$" ` ]
&& {<br>
cnt=0<br>
for i in `lpstat $pra | awk '{ print $1 }' `<br>
do<br>
cnt=`expr $cnt + 1`<br>
cancel $i<br>
done<br>
[ $cnt -eq "0" ] && {<br>
echo<br>
echo "JOBS for PRINTER "$pra" DO NOT EXIST Press
<ENTER> to Retu<br>
} || {<br>
echo<br>
true<br>
echo "Press <ENTER> to return to Menu"<br>
true<br>
}<br>
read me<br>
} || {<br>
[ -n "$pra" ] && {<br>
echo;echo "PRINTER "$pra" DOES NOT EXIST Press
<ENTER> to Return t<br>
read me<br>
}<br>
}<br>
;;<br>
X|x)<br>
</tt><br>
<pre class="moz-signature" cols="360">--
Steve Fabac
S.M. Fabac & Associates
816/765-1670</pre>
</body>
</html>
--------------070104090709070903010300--
|
|
|
0
|
|
|
|
Reply
|
Steve
|
3/2/2011 10:17:59 PM
|
|
This is a multi-part message in MIME format.
--------------020007070305070608030804
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
dthacker wrote:
> On Feb 9, 5:52 pm, "Steve M. Fabac, Jr." <smfa...@att.net> wrote:
>
>> dthacker wrote:
>>
>>> OS: Openserver 5.0.5
>>> Task: add a remote printer via rlpconf or scoadmin
>>> What should happen: printer queue should show up in output of lpstat
>>> -t
>>> What's happening instead: proper entries are created in /etc/printcap,
>>> var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
>>> run lpstat -t the printer does not show up.
>>> ---output of lpstat -t-----
>>> scheduler is running
>>> no system default destination
>>> device for s093ptr002: /dev/lp0
>>> device for s093ptr003: s093ptr003@s093ptr003
>>> s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
>>> printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
>>> available.
>>> ---end----
>>>
>>> When I attempt to start scoadmin printer, I'm getting this in /var/
>>> adm/syslog
>>> ----tail of syslog-----
>>> Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
>>> {s093ptr003} err
>>> or SCO_OFACE_MSG_ERROR {error
>>> {{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
>>> eral failure occurred in processing attribute printerDescription}}
>>> {SCO_NONSTD_C
>>> MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
>>> TO FIX: Use the "lpstat -p all" command to list all known
>>> printers}}}}
>>>
>>> I had to delete a badly configured queue with the same name
>>> (s093ptr003) before attempting to create this one. I used the
>>> scoadmin printer tool to delete the old queue. I've also found that
>>> if I manually delete the entries in printcap, lpd and lp/printers,
>>> scoadmin will start just fine. Ideas?
>>>
>>> Thanks in advance.
>>>
>>> Dave
>>>
>> Dave,
>>
>> I have always felt that the SCO rlp was a poor choice. See this
>> post on using rlpr:http://preview.tinyurl.com/6dwq49e
>>
>>
> Steve
>
> rlpr looks interesting, but I'm not sure can take 140 servers down
> that road right now. In the meantime, I'm still looking for a
> configuration file for scoadmin printers that might explain the error
> message I'm receiving.
>
> TIA
>
> Dave
>
>
>
>
Dave,
You have the same printer problem on 140 servers? or just one? Change
the one with the problem and you will wonder why you waited. I know that
I resisted using netcat for the longest time and after I converted on
system I became a true believer and apostle.
On a customer's SCO 5.0.5 system after I installed OSS646C (April
2008), the customer complained that the system was real slow and would
not shut down and reboot. When I logged in and checked there were
repeated messages in syslog:
"unix lpd[9999] unknown printer: (BSD format)" repeated over and over
10-20 times per second and inflated syslog to over 240Mb..
Removing OSS646C stopped the error message. Searching on the problem
revealed OSS663a the lpd daemon patch (specific to 5.0.6) that installed
after OSS646C was reinstalled and that fixed the problem of unknown
printer messages logged to syslog.
> Dear SCO Customer,
>
> Support Level Supplement (SLS) OSS663A, the LPD supplement for
> OpenServer 5.0.6 with OSS646, addresses a problem that
> occurs when either OSS646a or OSS646b is installed on an
> OpenServer 5.0.6 system with lpd printers defined.
>
> With OSS646 installed, lpd has a problem parsing
> /etc/printcap that results in a lot of entries in the
> syslog about unknown printer, similar to this:
>
> Jul 24 15:16:27 scosysv lpd[9160]: unknown printer: 026
Maybe your problem is related to OSS646C recently installed?
What I dislike with SCO's rlp is that lpstat -t has to go out to each
printer host and ask for the printer's status. One printer, no problem.
40 printers forget it. Also the problems with lpstat with rlp broke my
printer administration menu:
PRINTER=laser
PRINTER CONTROL MENU FOR smf
1) ENABLE A PRINTER
2) DISABLE A PRINTER
3) CHANGE PRINTERS
4) KILL A PRINT REQUEST
5) MOVE PRINT REQUESTS FROM
ONE PRINTER TO ANOTHER
6) PRINTER STATUS
7) RESTART PRINTERS
8) KILL ALL JOBS ON SPECIFIED PRINTER
X) EXIT
PLEASE SELECT (or 'H' for HELP):
Nearly all of the above choices rely on using output of lpstat -p to get
a working list of printers and jobs. The hang-up of a single rlp host
prevents the scripts from running as designed.
# PRINTER CONTROL MENU
# @(#) LPCMENU 1.6 9/6/96"
#
lplist() {
lpstat -p | awk '{ printf "%-14s", $2
for (i = 2; i <= NF; i++ ) {
if ( $i == "enabled" )
printf "%8s\n", $i
if ( $i == "disabled") {
printf "%8s:", $i
getline
printf "%s\n", $0 } } } ';
}
prtpth=/usr/spool/lp/admins/lp/interfaces
trap '' 2
while(true)
do
tput clear
tput smso
echo "
PRINTER=$LPDEST
tput cuu1
echo " PRINTER CONTROL MENU FOR
$USER
tput rmso
cat <<!
....
2)
tput clear;
echo "LIST OF PRINTERS......";
echo "===============================";
lplist
# echo "";
echo "===============================";
echo "SELECT PRINTER TO DISABLE : ";
read pra;
if [ `lpstat -p $pra | awk ' { print $2 } ' | grep
"${pra:-null}$" ` ]
then
echo "Enter a Reason for disabling " $pra "-c"
read reason
disable -r"${reason}" $pra;
elif test -n "$pra"
then
echo "PRINTER "$pra" DOES NOT EXIST Press <ENTER> to Return to
Menu";
read pra;
fi
echo;;
....
8)
tput clear
echo " THE FOLLOWING IS A LIST OF ACTIVE PRINT REQUESTS..... ";
echo "======================================================";
lpstat -u
echo "======================================================";
echo "SELECT PRINTER TO CANCLE : \c"
read pra
[ `lpstat -p | awk ' { print $2 } ' | grep "${pra:-null}$" ` ] && {
cnt=0
for i in `lpstat $pra | awk '{ print $1 }' `
do
cnt=`expr $cnt + 1`
cancel $i
done
[ $cnt -eq "0" ] && {
echo
echo "JOBS for PRINTER "$pra" DO NOT EXIST Press <ENTER>
to Retu
} || {
echo
true
echo "Press <ENTER> to return to Menu"
true
}
read me
} || {
[ -n "$pra" ] && {
echo;echo "PRINTER "$pra" DOES NOT EXIST Press <ENTER> to
Return t
read me
}
}
;;
X|x)
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
--------------020007070305070608030804
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
dthacker wrote:
<blockquote
cite="mid21442bd4-2b84-47d2-9182-e61c2f109468@w7g2000pre.googlegroups.com"
type="cite">
<pre wrap="">On Feb 9, 5:52 pm, "Steve M. Fabac, Jr." <a
class="moz-txt-link-rfc2396E" href="mailto:smfa...@att.net"><smfa...@att.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">dthacker wrote:
</pre>
<blockquote type="cite">
<pre wrap="">OS: Openserver 5.0.5
Task: add a remote printer via rlpconf or scoadmin
What should happen: printer queue should show up in output of lpstat
-t
What's happening instead: proper entries are created in /etc/printcap,
var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
run lpstat -t the printer does not show up.
---output of lpstat -t-----
scheduler is running
no system default destination
device for s093ptr002: /dev/lp0
device for s093ptr003: s093ptr003@s093ptr003
s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
available.
---end----
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap=""> When I attempt to start scoadmin printer, I'm getting this in /var/
adm/syslog
----tail of syslog-----
Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
{s093ptr003} err
or SCO_OFACE_MSG_ERROR {error
{{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
eral failure occurred in processing attribute printerDescription}}
{SCO_NONSTD_C
MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
TO FIX: Use the "lpstat -p all" command to list all known
printers}}}}
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">I had to delete a badly configured queue with the same name
(s093ptr003) before attempting to create this one. I used the
scoadmin printer tool to delete the old queue. I've also found that
if I manually delete the entries in printcap, lpd and lp/printers,
scoadmin will start just fine. Ideas?
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">Thanks in advance.
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">Dave
</pre>
</blockquote>
<pre wrap="">Dave,
I have always felt that the SCO rlp was a poor choice. See this
post on using rlpr:<a class="moz-txt-link-freetext"
href="http://preview.tinyurl.com/6dwq49e">http://preview.tinyurl.com/6dwq49e</a>
</pre>
</blockquote>
<pre wrap=""><!---->Steve
rlpr looks interesting, but I'm not sure can take 140 servers down
that road right now. In the meantime, I'm still looking for a
configuration file for scoadmin printers that might explain the error
message I'm receiving.
TIA
Dave
</pre>
</blockquote>
Dave,<br>
<br>
You have the same printer problem on 140 servers? or just one? Change
the one with the problem and you will wonder why you waited. I know
that I resisted using netcat for the longest time and after I converted
on system I became a true believer and apostle.<br>
<br>
On a customer's SCO 5.0.5 system after I installed OSS646C (April
2008), the customer complained that the system was real slow and would
not shut down and reboot. When I logged in and checked there were
repeated messages in syslog: <br>
<br>
"unix lpd[9999] unknown printer: (BSD format)" repeated over and over
10-20 times per second and inflated syslog to over 240Mb..<br>
<br>
Removing OSS646C stopped the error message. Searching on the problem
revealed OSS663a the lpd daemon patch (specific to 5.0.6) that
installed after OSS646C was reinstalled and that fixed the problem of
unknown printer messages logged to syslog. <br>
<br>
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span"
style="font-family: 'Courier New',Arial,Helvetica,Tahoma,sans-serif; font-size: 13px;">
<pre> Dear SCO Customer,
Support Level Supplement (SLS) OSS663A, the LPD supplement for
OpenServer 5.0.6 with OSS646, addresses a problem that
occurs when either OSS646a or OSS646b is installed on an
OpenServer 5.0.6 system with lpd printers defined.
With OSS646 installed, lpd has a problem parsing
/etc/printcap that results in a lot of entries in the
syslog about unknown printer, similar to this:
Jul 24 15:16:27 scosysv lpd[9160]: unknown printer: 026 </pre>
</span></span></blockquote>
<br>
<br>
Maybe your problem is related to OSS646C recently installed? <br>
<br>
What I dislike with SCO's rlp is that lpstat -t has to go out to each
printer host and ask for the printer's status. One printer, no problem.
40 printers forget it. Also the problems with lpstat with rlp broke my
printer administration menu:<br>
<br>
<tt>
PRINTER=laser <br>
PRINTER CONTROL MENU FOR smf
<br>
<br>
<br>
1) ENABLE A PRINTER<br>
<br>
2) DISABLE A PRINTER<br>
<br>
3) CHANGE PRINTERS<br>
<br>
4) KILL A PRINT REQUEST<br>
<br>
5) MOVE PRINT REQUESTS FROM<br>
ONE PRINTER TO ANOTHER<br>
<br>
6) PRINTER STATUS<br>
<br>
7) RESTART PRINTERS<br>
<br>
8) KILL ALL JOBS ON SPECIFIED PRINTER<br>
<br>
X) EXIT<br>
PLEASE SELECT (or 'H' for HELP): <br>
<br>
Nearly all of the above choices rely on using output of lpstat -p to
get a working list of printers and jobs. The hang-up of a single rlp
host prevents the scripts from running as designed.<br>
<br>
# PRINTER CONTROL MENU<br>
# @(#) LPCMENU 1.6 9/6/96"<br>
#<br>
lplist() {<br>
lpstat -p | awk '{ printf "%-14s", $2<br>
for (i = 2; i <= NF; i++ ) {<br>
if ( $i == "enabled" )<br>
printf "%8s\n", $i <br>
if ( $i == "disabled") {<br>
printf "%8s:", $i<br>
getline<br>
printf "%s\n", $0 } } } ';<br>
}<br>
prtpth=/usr/spool/lp/admins/lp/interfaces<br>
trap '' 2<br>
while(true)<br>
do<br>
tput clear<br>
tput smso<br>
echo "
PRINTER=$LPDEST <br>
tput cuu1<br>
echo " PRINTER CONTROL MENU FOR
$USER <br>
tput rmso<br>
cat <<!<br>
....<br>
2)<br>
tput clear;<br>
echo "LIST OF PRINTERS......";<br>
echo "===============================";<br>
lplist<br>
# echo "";<br>
echo "===============================";<br>
echo "SELECT PRINTER TO DISABLE : ";<br>
read pra;<br>
if [ `lpstat -p $pra | awk ' { print $2 } ' | grep
"${pra:-null}$" ` ] <br>
then<br>
echo "Enter a Reason for disabling " $pra "-c"<br>
read reason<br>
disable -r"${reason}" $pra;<br>
elif test -n "$pra"<br>
then<br>
echo "PRINTER "$pra" DOES NOT EXIST Press <ENTER> to
Return to Menu";<br>
read pra;<br>
fi<br>
echo;;<br>
....<br>
8)<br>
tput clear<br>
echo " THE FOLLOWING IS A LIST OF ACTIVE PRINT REQUESTS..... ";<br>
echo "======================================================";<br>
lpstat -u<br>
echo "======================================================";<br>
echo "SELECT PRINTER TO CANCLE : \c"<br>
read pra<br>
[ `lpstat -p | awk ' { print $2 } ' | grep "${pra:-null}$" ` ]
&& {<br>
cnt=0<br>
for i in `lpstat $pra | awk '{ print $1 }' `<br>
do<br>
cnt=`expr $cnt + 1`<br>
cancel $i<br>
done<br>
[ $cnt -eq "0" ] && {<br>
echo<br>
echo "JOBS for PRINTER "$pra" DO NOT EXIST Press
<ENTER> to Retu<br>
} || {<br>
echo<br>
true<br>
echo "Press <ENTER> to return to Menu"<br>
true<br>
}<br>
read me<br>
} || {<br>
[ -n "$pra" ] && {<br>
echo;echo "PRINTER "$pra" DOES NOT EXIST Press
<ENTER> to Return t<br>
read me<br>
}<br>
}<br>
;;<br>
X|x)<br>
</tt><br>
<pre class="moz-signature" cols="360">--
Steve Fabac
S.M. Fabac & Associates
816/765-1670</pre>
</body>
</html>
--------------020007070305070608030804--
|
|
|
0
|
|
|
|
Reply
|
Steve
|
3/3/2011 2:22:27 AM
|
|
On 3/2/2011 5:17 PM, Steve M. Fabac, Jr. wrote:
I don't know why, but the last two message from you appear blank in
thunderbird. But when I view source I can see there is content.
Something borked the mime formatting maybe?
It prevented this reply from including any quoted material too. I didn't
strip it.
--
bkw
|
|
|
0
|
|
|
|
Reply
|
 brian109 (760)
|
3/3/2011 5:28:21 PM
|
|
On 3/3/2011 12:28 PM, Brian K. White wrote:
> On 3/2/2011 5:17 PM, Steve M. Fabac, Jr. wrote:
>
> I don't know why, but the last two message from you appear blank in
> thunderbird. But when I view source I can see there is content.
> Something borked the mime formatting maybe?
>
> It prevented this reply from including any quoted material too. I didn't
> strip it.
>
Might be because the top headers declare multipart without defining any
boundary.
Your email, at least as I received it which might not be the way you
sent it, has:
Mime-Version: 1.0
Content-Type: multipart/alternative;
If it's going to be a multipart mime, then it should define a boundary
like so:
MIME-Version: 1.0
Content-Type: multipart/related; boundary=226752340229846
Or, if it's not going to be a multipart then it should not declare
itself to be a multipart, like so:
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Or for plain text by simply not including any mime or content-type
headers at all.
--
bkw
|
|
|
0
|
|
|
|
Reply
|
brian109 (760)
|
3/3/2011 5:47:19 PM
|
|
Brian K. White wrote:
> On 3/2/2011 5:17 PM, Steve M. Fabac, Jr. wrote:
>
> I don't know why, but the last two message from you appear blank in
> thunderbird. But when I view source I can see there is content.
> Something borked the mime formatting maybe?
>
> It prevented this reply from including any quoted material too. I
> didn't strip it.
>
Yeah, I see that too. I'm not sure what is going on. I use Thuderbird on
my XP system for e-mail. I have been switching between plane text and
html based upon the need to include pictures in-line. This reply is
being composed html. I'll switch to plane text and send a second reply.
to see what happens.
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
|
|
|
0
|
|
|
|
Reply
|
 smfabac (423)
|
3/3/2011 5:57:28 PM
|
|
Brian K. White wrote:
> On 3/2/2011 5:17 PM, Steve M. Fabac, Jr. wrote:
>
> I don't know why, but the last two message from you appear blank in
> thunderbird. But when I view source I can see there is content.
> Something borked the mime formatting maybe?
>
> It prevented this reply from including any quoted material too. I didn't
> strip it.
>
Yeah, I see that too. I'm not sure what is going on. I use Thuderbird
on my XP system for e-mail. I have been switching between plain text
and html based upon the need to include pictures in-line. This reply
is being composed plain text. (not plane - oops)
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
|
|
|
0
|
|
|
|
Reply
|
smfabac (423)
|
3/3/2011 6:00:16 PM
|
|
dthacker wrote:
> On Feb 9, 5:52 pm, "Steve M. Fabac, Jr." <smfa...@att.net> wrote:
>> dthacker wrote:
>>> OS: Openserver 5.0.5
>>> Task: add a remote printer via rlpconf or scoadmin
>>> What should happen: printer queue should show up in output of lpstat
>>> -t
>>> What's happening instead: proper entries are created in /etc/printcap,
>>> var/spool/lpd and /var/spool/lp/admins/lp/printers. However when I
>>> run lpstat -t the printer does not show up.
>>> ---output of lpstat -t-----
>>> scheduler is running
>>> no system default destination
>>> device for s093ptr002: /dev/lp0
>>> device for s093ptr003: s093ptr003@s093ptr003
>>> s093ptr002 accepting requests since Sat Feb 13 12:42:23 2010
>>> printer s093ptr002 is idle. enabled since Sat Feb 13 12:42:23 2010.
>>> available.
>>> ---end----
>>> When I attempt to start scoadmin printer, I'm getting this in /var/
>>> adm/syslog
>>> ----tail of syslog-----
>>> Feb 9 10:28:36 scosysv syslog: SCOADM: localhost {sco_printer}
>>> {s093ptr003} err
>>> or SCO_OFACE_MSG_ERROR {error
>>> {{SCO_OSA_ERR_PROCESSING_FAILURE_ON_ATTRIBUTE {Gen
>>> eral failure occurred in processing attribute printerDescription}}
>>> {SCO_NONSTD_C
>>> MDS_ERR_lpstat {UX:lpstat: ERROR: Printer "s093ptr003" does not exist.
>>> TO FIX: Use the "lpstat -p all" command to list all known
>>> printers}}}}
>>> I had to delete a badly configured queue with the same name
>>> (s093ptr003) before attempting to create this one. I used the
>>> scoadmin printer tool to delete the old queue. I've also found that
>>> if I manually delete the entries in printcap, lpd and lp/printers,
>>> scoadmin will start just fine. Ideas?
>>> Thanks in advance.
>>> Dave
>> Dave,
>>
>> I have always felt that the SCO rlp was a poor choice. See this
>> post on using rlpr:http://preview.tinyurl.com/6dwq49e
>>
> Steve
>
> rlpr looks interesting, but I'm not sure can take 140 servers down
> that road right now. In the meantime, I'm still looking for a
> configuration file for scoadmin printers that might explain the error
> message I'm receiving.
>
> TIA
>
> Dave
>
>
>
Dave,
You have the same printer problem on 140 servers? or just one? Change
the one with the problem and you will wonder why you waited. I know that
I resisted using netcat for the longest time and after I converted one
system I became a true believer and apostle.
On a customer's SCO 5.0.5 system after I installed OSS646C (April 2008),
the customer complained that the system was real slow and would not shut
down and reboot. When I logged in and checked there were repeated messages
in syslog: "unix lpd[9999] unknown printer: (BSD format)" repeated over
and over 10-20 times per second and inflated syslog to over 240Mb.
Removing OSS646C stopped the error message. Searching on the problem
revealed OSS663a the lpd daemon patch (specific to 5.0.6) that installed
after OSS646C was reinstalled and that fixed the problem of unknown printer
messages logged to syslog.
>>
>> Dear SCO Customer,
>>
>> Support Level Supplement (SLS) OSS663A, the LPD supplement for
>> OpenServer 5.0.6 with OSS646, addresses a problem that
>> occurs when either OSS646a or OSS646b is installed on an
>> OpenServer 5.0.6 system with lpd printers defined.
>>
>> With OSS646 installed, lpd has a problem parsing
>> /etc/printcap that results in a lot of entries in the
>> syslog about unknown printer, similar to this:
>>
>> Jul 24 15:16:27 scosysv lpd[9160]: unknown printer: 026
Maybe your problem is related to OSS646C recently installed?
What I dislike with SCO's rlp is that lpstat -t has to go out to each
printer host and ask for the printer's status. One printer, no problem.
40 printers forget it. Also the problems with lpstat with rlp broke my
printer administration menu:
>
> PRINTER=laser
> PRINTER CONTROL MENU FOR smf
>
>
> 1) ENABLE A PRINTER
>
> 2) DISABLE A PRINTER
>
> 3) CHANGE PRINTERS
>
> 4) KILL A PRINT REQUEST
>
> 5) MOVE PRINT REQUESTS FROM
> ONE PRINTER TO ANOTHER
>
> 6) PRINTER STATUS
>
> 7) RESTART PRINTERS
>
> 8) KILL ALL JOBS ON SPECIFIED PRINTER
>
> X) EXIT
> PLEASE SELECT (or 'H' for HELP):
Nearly all of the above choices rely on using output of lpstat -p
or lpstat -u to get a working list of printers and jobs. The hang-up
of a single rlp host and/or the format returned prevents the scripts
from running as designed.
# PRINTER CONTROL MENU
# @(#) LPCMENU 1.6 9/6/96"
#
lplist() {
lpstat -p | awk '{ printf "%-14s", $2
for (i = 2; i <= NF; i++ ) {
if ( $i == "enabled" )
printf "%8s\n", $i
if ( $i == "disabled") {
printf "%8s:", $i
getline
printf "%s\n", $0 } } } ';
}
prtpth=/usr/spool/lp/admins/lp/interfaces
trap '' 2
while(true)
do
tput clear
tput smso
echo " PRINTER=$LPDEST
tput cuu1
echo " PRINTER CONTROL MENU FOR $USER
tput rmso
cat <<!
....
2)
tput clear;
echo "LIST OF PRINTERS......";
echo "===============================";
lplist
# echo "";
echo "===============================";
echo "SELECT PRINTER TO DISABLE : ";
read pra;
if [ `lpstat -p $pra | awk ' { print $2 } ' | grep "${pra:-null}$" ` ]
then
echo "Enter a Reason for disabling " $pra "-c"
read reason
disable -r"${reason}" $pra;
elif test -n "$pra"
then
echo "PRINTER "$pra" DOES NOT EXIST Press <ENTER> to Return to Menu";
read pra;
fi
echo;;
....
8)
tput clear
echo " THE FOLLOWING IS A LIST OF ACTIVE PRINT REQUESTS..... ";
echo "======================================================";
lpstat -u
echo "======================================================";
echo "SELECT PRINTER TO CANCLE : \c"
read pra
[ `lpstat -p | awk ' { print $2 } ' | grep "${pra:-null}$" ` ] && {
cnt=0
for i in `lpstat $pra | awk '{ print $1 }' `
do
cnt=`expr $cnt + 1`
cancel $i
done
[ $cnt -eq "0" ] && {
echo
echo "JOBS for PRINTER "$pra" DO NOT EXIST Press <ENTER> to Return to Menu"
} || {
echo
true
echo "Press <ENTER> to return to Menu"
true
}
read me
} || {
[ -n "$pra" ] && {
echo;echo "PRINTER "$pra" DOES NOT EXIST Press <ENTER> to Return to Menu"
read me
}
}
;;
X|x)
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
|
|
|
0
|
|
|
|
Reply
|
smfabac (423)
|
3/3/2011 6:15:33 PM
|
|
On 3/3/2011 1:00 PM, Steve M. Fabac, Jr. wrote:
> Brian K. White wrote:
>> On 3/2/2011 5:17 PM, Steve M. Fabac, Jr. wrote:
>>
>> I don't know why, but the last two message from you appear blank in
>> thunderbird. But when I view source I can see there is content.
>> Something borked the mime formatting maybe?
>>
>> It prevented this reply from including any quoted material too. I
>> didn't strip it.
>>
>
> Yeah, I see that too. I'm not sure what is going on. I use Thuderbird
> on my XP system for e-mail. I have been switching between plain text
> and html based upon the need to include pictures in-line. This reply
> is being composed plain text. (not plane - oops)
>
>
One of my replies seems to be delayed or lost.
I pointed out that the blank mails had content-type that declared
multipart without defining any boundary.
The last two from you were fine.
--
bkw
|
|
|
0
|
|
|
|
Reply
|
brian109 (760)
|
3/3/2011 6:44:50 PM
|
|
Brian K. White wrote:
> On 3/3/2011 12:28 PM, Brian K. White wrote:
>> On 3/2/2011 5:17 PM, Steve M. Fabac, Jr. wrote:
>>
>> I don't know why, but the last two message from you appear blank in
>> thunderbird. But when I view source I can see there is content.
>> Something borked the mime formatting maybe?
>>
>> It prevented this reply from including any quoted material too. I didn't
>> strip it.
>>
>
> Might be because the top headers declare multipart without defining any
> boundary.
> Your email, at least as I received it which might not be the way you
> sent it, has:
> Mime-Version: 1.0
> Content-Type: multipart/alternative;
>
> If it's going to be a multipart mime, then it should define a boundary
> like so:
> MIME-Version: 1.0
> Content-Type: multipart/related; boundary=226752340229846
>
> Or, if it's not going to be a multipart then it should not declare
> itself to be a multipart, like so:
> Mime-Version: 1.0
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
>
> Or for plain text by simply not including any mime or content-type
> headers at all.
>
I can't explain it. My version of Thunderbird is version 1.5.0.9 (20061207)
maybe time to upgrade?
I have not upgraded because I hate feature creep and changes in the
look and feel navigating the product. I think I may have upgraded at
one time but was unhappy and restored my system from a backup to get
rid of the upgrade. If the problem is only on mime sent to C.U.S.M.
I'll be sure to switch to plain text before posting. I have not received
a complaint about html mail exchanged with clients.
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
|
|
|
0
|
|
|
|
Reply
|
smfabac (423)
|
3/3/2011 8:49:08 PM
|
|
|
13 Replies
163 Views
(page loaded in 0.276 seconds)
Similiar Articles: lpstat -p question - comp.unix.solarisLONGEST LIST - comp.parallel.mpi lpstat -p question - comp.unix.solaris LONGEST LIST - comp.parallel.mpi... Post Question Groups ... Problems adding remote printer - comp ... lpsched issues - comp.sys.hp.hpux... Jan Gerrit my steps 1) add ip to hosts file 2) go to sam to add a remote printer (i ... Question : How to enable "lpsched" in solaris 10 ... Solaris 10 printer problems ... Printing via Windows XP - comp.unix.solaris... printing with my home network and am having problems! My HP psc750 printer ... or use admintool or printmgr to "add access . . ." or "create new remote printer". remote printing blank pages - comp.sys.sun.adminEOM 7.1.7 - Adding Form Feed - comp.sys.unisys remote printing blank pages ... not R2) machine which has problems with redirected printing. Clients connecting via Remote ... how to set up printer on Solaris 10? - comp.unix.solaris ...use # /usr/sbin/printmgr menu choose <printer> <add ... Dont know if windows accepts remote printing by default. ... Solaris 10 printer problems - comp.unix.solaris Solaris 10 ... HP/UX printing queues - comp.sys.hp.hpuxA route add command may have to be run ... Communications Good troubleshooting of printing problems ... printing is taking place, make sure that the remote printer ... Solaris 10 print service start and generate a lot of tmp files ...But every time if you add a new printer, the print ... sparc workstation with solaris 10 and remote printing ... 10 - comp.unix.solaris Solaris 10 printer problems ... Ipsec in solaris 9 - comp.unix.solarisHi, I have some problems with ipsec realization in ... list: permit ip pix_net solaris_net When I add ... remote printer prints blank pages - comp.sys.sun.admin This is ... passwd file problem,,,help - comp.unix.solarisSolaris 10 printer problems - comp.unix.solaris Netgroup Access problem (PASSWD) - comp ... unix.solaris | Computer Group Hello All, I modified the passwd file on a remote ... HP-UX 10.20 - comp.sys.hp.hpuxCan I obtain a remote graphic access (say with Xnest ... NFS problems on hp-ux - comp.sys.hp.hpux We have 3 HP-UX ... Need Help Adding Printer HPUX 10.20 - comp.sys.hp.hpux how to ... A problem in IPsec - comp.unix.solaris... label1" local_addr 135.254.225.89 remote ... SLT: 28500 seconds of post-add lifetime. SLT: 0 ... Filemaker 7 Idle disconnect problems.. - comp.databases ... Solaris 10 Jumpstart issue - comp.unix.solarisJust to add.. I found the following OS requirements ... with Jumpstart - comp.unix.solaris Solaris 10 printer problems ... UNIX and Linux Forums I'm trying to jumpstart my remote ... Incredibly slow! - comp.graphics.api.opengl... instead (which gives "NVIDIA corp"), then post adding ... very slow PDF file printing - comp.text.pdf I often ... Recently, very slow internet problems are becoming more ... Overcoming insufficient permissions for PDF image extraction to ...... see photographs and diagrams of the problems ... folks is, if all these five desires (printing pages, converting pages, adding ... of RIAA or MPAA, there's still a remote ... client: searching for jumpstart directory: not found. No entry in ...always add the -v flag to your boot install whatever ... Sun's attempt at remote console for their own x86 ... to stay away from GUIs I seem to have less >>> problems ... How to Add a Printer to a Remote Desktop | eHow.comRemote Desktop is included with Windows XP Professional and enables connection to a computer from a remote location through the Internet. With Remote Desktop, work on ... How to install a printer driver locally for a remote printer in ...Describes how to install a remote printer driver on a local computer. ... Double-click Add Printer to start the Add Printer Wizard, and then click ... 7/10/2012 10:32:48 AM
|
Search |
Post Question |
Groups |
Stream |
About |
Register
1 followers. 