12-09-2011
The above erros looks to be related with SCSI device. Probe time below states, it was trying to check why it has happened, it failed with timeout.
what operations were you doing there?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:cool: I need some assistance please. I'm setting up a SunOS 5.6 server and sofar I'm able to telnet into the unit but unable to telnet from it. Can anyone help me with this problem. When attempting to telnet from my SunOs to client
terminal I'm receving the following error, "Unable to connect to... (3 Replies)
Discussion started by: sharris82
3 Replies
2. HP-UX
Hi friend,
I'm facing a problem to access the console and telnet to the HP ux 11 server due to the system file is full. How to access this server via single mode and how to mount the folder / and folder /var?
thanks.
vestro (1 Reply)
Discussion started by: vestro
1 Replies
3. AIX
Hi,
I encountered error when I telnet to my server.
Error is as follows:
telnetd: /bin/login: The file access permissions do not allow the specified action
I am able to ssh into my server and I have checked/verified /etc/security and /etc/inetd.conf. I restarted the inetd subsystem via... (1 Reply)
Discussion started by: chongkls77
1 Replies
4. Solaris
Hi guys,
After changing my workstation from domain rsm.renesas.com to my.renesas.local, I was unable to telnet to 1 of our Sun Solaris servers.
There r errors in the messages file:
Aug 15 17:35:26 rsmsso1.svc.rsm.renesas.com inetd: warning: can't verify hostname:... (12 Replies)
Discussion started by: *Jess*
12 Replies
5. UNIX for Dummies Questions & Answers
Dear All,
I have Compaq Alpha server running UNIX OS. with Old Hardware specification.
I had FTP conncetion using IP Switch ( FTP client ) to the Unix server in order to copy some files to my workstation. one day after closing the connection we noted that IT operations are not able to... (8 Replies)
Discussion started by: Arehan
8 Replies
6. SuSE
Hi forum,
I face a strange issue. I'm able to telnet as root with ssh.
But I'm not able to telnet (non-ssh) as root to my Suse 10 machine.
Can someone please point to significant files where I need to make changes for Suse 10 machine and resolve this issue.
Thanks in advance. (2 Replies)
Discussion started by: anilgurwara
2 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have two linux boxes and due to some reasons I have reinstalled OS in one of them. Now Iam unable to telnet one of them. I have included entries in /etc/hosts in both and Iam able to ping each other.
Am I missing anything here or I we need to install/activate telnet server ?
Thanks... (2 Replies)
Discussion started by: ssuhaib
2 Replies
8. UNIX for Dummies Questions & Answers
Hi I am working in Solaris 10 and I want to monitor logs for every telnet/ssh session that tries to connect to the server. I need these logs to be generated in a file that I can fetch using ftp.
I am a new user and a stepwise detail will be great
BR
saGGee (3 Replies)
Discussion started by: saggee
3 Replies
9. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
10. Solaris
hi Everyone
telnet and ssh not working in Solaris 8 .... but it pinging.... i also checked
/etc/services
/etc/inet/inetd.conf
ps -ef | grep telnet
ans default router ... everythinking is ok .... when i connect telnet then suddently closed ... and ssh is connection refused ...
help... (1 Reply)
Discussion started by: coolboys
1 Replies
LEARN ABOUT SUSE
sane-find-scanner
sane-find-scanner(1) SANE Scanner Access Now Easy sane-find-scanner(1)
NAME
sane-find-scanner - find SCSI and USB scanners and their device files
SYNOPSIS
sane-find-scanner [-h|-?] [-v] [-q] [-p] [-f] [-F filename] [devname]
DESCRIPTION
sane-find-scanner is a command-line tool to find SCSI and USB scanners and determine their Unix device files. Its primary aim is to make
sure that scanners can be detected by SANE backends.
For SCSI scanners, it checks the default generic SCSI device files (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI
inquiry command and looking for a device type of "scanner" or "processor" (some old HP scanners seem to send "processor"). So
sane-find-scanner will find any SCSI scanner connected to those default device files even if it isn't supported by any SANE backend.
For USB scanners, first the USB kernel scanner device files (e.g. /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner) are tested.
The files are opened and the vendor and device ids are determined, if the operating system supports this feature. Currently USB scanners
are only found this way if they are supported by the Linux scanner module or the FreeBSD or OpenBSD uscanner driver. After that test,
sane-find-scanner tries to scan for USB devices found by the USB library libusb (if available). There is no special USB class for scanners,
so the heuristics used to distinguish scanners from other USB devices is not perfect. sane-find-scanner also tries to find out the type of
USB chip used in the scanner. If detected, it will be printed after the vendor and product ids. sane-find-scanner will even find USB scan-
ners, that are not supported by any SANE backend.
sane-find-scanner won't find most parallel port scanners, or scanners connected to proprietary ports. Some parallel port scanners may be
detected by sane-find-scanner -p. At the time of writing this will only detect Mustek parallel port scanners.
OPTIONS
-h, -? Prints a short usage message.
-v Verbose output. If used once, sane-find-scanner shows every device name and the test result. If used twice, SCSI inquiry informa-
tion and the USB device descriptors are also printed.
-q Be quiet. Print only the devices, no comments.
-p Probe parallel port scanners.
-f Force opening all explicitly given devices as SCSI and USB devices. That's useful if sane-find-scanner is wrong in determining the
device type.
-F filename
filename is a file that contains USB descriptors in the format of /proc/bus/usb/devices as used by Linux. sane-find-scanner tries
to identify the chipset(s) of all USB scanners found in such a file. This option is useful for developers when the output of "cat
/proc/bus/usb/devices" is available but the scanner itself isn't.
devname Test device file "devname". No other devices are checked if devname is given.
EXAMPLE
sane-find-scanner -v
Check all SCSI and USB devices for available scanners and print a line for every device file.
sane-find-scanner /dev/scanner
Look for a (SCSI) scanner only at /dev/scanner and print the result.
sane-find-scanner -p
Probe for parallel port scanners.
SEE ALSO
sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1), sane-"backendname"(5)
AUTHOR
Oliver Rauch, Henning Meier-Geinitz and others
SUPPORTED PLATFORMS
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel, libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the vendor
and device ids only works with Linux or libusb.
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris, FreeBSD, NetBSD, OpenBSD, and HP-UX.
BUGS
No support for most parallel port scanners yet.
Detection of USB chipsets is limited to a few chipsets.
13 Jul 2008 sane-find-scanner(1)