Get APLawrence.com by RSSHPNP and getone getmany (SNMP)
What is this stuff?
If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):
From - Wed Oct 13 17:25:08 1999
Xref: world comp.unix.sco.misc:107391
Path: world!newsfeed.mathworks.com!news.maxwell.syr.edu!easynet-tele!easynet.net!remarQ-uK!rQdQ!supernews.com!remarQ.com!corp.supernews.com!not-for-mail
From: Jeff Liebermann <jeffl@comix.santa-cruz.ca.us>
Newsgroups: comp.unix.sco.misc
Subject: Re: Can't print to HP Printserver
Date: Wed, 13 Oct 1999 10:56:01 -0700
Organization: Committee To Maintain an Independent Xenix
Lines: 33
Message-ID: <4cUEODUzMn4O33h+=ahSMHo8ZKaN@4ax.com>
References: <000f01bf14f8$a2a17b40$0a0000c0@root> <3804ADF8.AAAD37F9@summit-soft.com>
Reply-To: jeffl@comix.santa-cruz.ca.us
X-Complaints-To: newsabuse@supernews.com
X-Newsreader: Forte Agent 1.6/32.525
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mozilla-Status: 8010
On Wed, 13 Oct 1999 11:06:16 -0500, Ric Pennington <ricp@summit-soft.com>
wrote:
>Try renaming getone in the /etc directory
Let me explain *HOW* that works. getone is the program that retreives
SNMP information from a network device. HPNP uses getone to detemine if
the print server is ready for action. However, HPNP was inscribed in the
days before 3 port servers and therefore *ASSUMES[1]* that the print
server has only one printer port. It therefore only check the first port
to see if the attached printer is ready to print. It ignores the other
two ports.
If you take the printer on the first port offline, HPNP will not print to
the other two ports until the first port printer is back online.
By renaming getone, the incredibly stupid HPNP program assumes that SNMP
is not installed on the system, and to therefore not bother asking the
print server if it's ready for action. It just *ASSUMES[1]* that it's
allways ready.
Incidentally, if you need some entertainment, try:
getmany IP_of_print_server public iso
On some printers, it will even tell you how many pages are left in the
paper bin.
[1]Assumption: The mother of all screwups.
--
Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
(831)421-6491 pgr (831)426-1240 fax (831)336-2558 home
http://www.cruzio.com/~jeffl WB6SSY
jeffl@comix.santa-cruz.ca.us jeffl@cruzio.com
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them.
I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
/Bofcusm/121.html copyright 1997-2004 (various authors) All Rights Reserved
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Get1=`ls -l /etc/getone | awk '{print $11}'`
mv $Get1 $Get1.bak
Rather than renaming getone in the /etc/directory,
which is just a symlink to the 'real' getone in
/opt/K/SCO/tcp/version/etc (and will be rebuilt the
next time custom repairs symlinks), follow the link
and rename the actual file.
Get1=`ls -l /etc/getone | awk '{print $11}'`
mv $Get1 $Get1.bak
Rather than renaming getone in the /etc/ directory,
which is just a symlink to the 'real' getone in
/opt/K/SCO/tcp/version/etc (and will be rebuilt the
next time custom repairs symlinks), follow the link
and rename the actual file.
Get1=`ls -l /etc/getone | awk '{print $11}'`
mv $Get1 $Get1.bak
Rather than renaming getone in the /etc/ directory,
which is just a symlink to the 'real' getone in
/opt/K/SCO/tcp/*/etc (and will be rebuilt the
next time custom repairs symlinks), follow the link
and rename the actual file.
Get1=`ls -l /etc/getone | awk '{print $11}'`
mv $Get1 $Get1.bak
Rather than renaming getone in the /etc/ directory,
which is just a symlink to the 'real' getone in
/opt/K/SCO/tcp/*/etc (and will be rebuilt the
next time custom repairs symlinks), follow the link
and rename the actual file.
Get1=`ls -l /etc/getone | awk '{print $11}'`
mv $Get1 $Get1.bak
Rather than renaming getone in the /etc/ directory,
which is just a symlink to the 'real' getone in
/opt/K/SCO/tcp/*/etc (and will be rebuilt the
next time custom repairs symlinks), follow the link
and rename the actual file.
Get1=`ls -l /etc/getone | awk '{print $11}'`
mv $Get1 $Get1.bak
---January 25, 2005
Rather than renaming getone in the /etc/ directory,
which is just a symlink to the 'real' getone in
/opt/K/SCO/tcp/*/etc (and will be rebuilt the
next time custom repairs symlinks), follow the link
and rename the actual file.
Get1=`ls -l /etc/getone | awk '{print $11}'`
mv $Get1 $Get1.bak
---January 25, 2005
---January 25, 2005
Rather than renaming getone in the /etc/ directory,
which is just a symlink to the 'real' getone in
/opt/K/SCO/tcp/*/etc (and will be rebuilt the
next time custom repairs symlinks), follow the link
and rename the actual file.
Get1=`ls -l /etc/getone | awk '{print $11}'`
mv $Get1 $Get1.bak
Rather than renaming getone in the /etc/ directory,
which is just a symlink to the 'real' getone in
/opt/K/SCO/tcp/*/etc (and will be rebuilt the
next time custom repairs symlinks), follow the link
and rename the actual file.
Get1=`ls -l /etc/getone | awk '{print $11}'`
mv $Get1 $Get1.bak
---January 25, 2005
Yeah, that's been argued before. Personally, I wouldn't use hpnp anyway (netcat is much more reliable). Anyway, some will say that they never let custom do anything by itself anyway. I'm not quite that difficult, though I do like to examine its proposed fixes before turning it loose.
But your point is valid and important to be aware of.
--TonyLawrence
Thu Jan 1 00:00:00 1970:
Thu Jan 1 00:00:00 1970:
Thu Jan 1 00:00:00 1970:
Thu Jan 1 00:00:00 1970:
Thu Jan 1 00:00:00 1970:
Thu Jan 1 00:00:00 1970:
Thu Jan 1 00:00:00 1970:
Thu Jan 1 00:00:00 1970:
Thu Jan 1 00:00:00 1970:
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar