Sponsored Content
Full Discussion: coming out from vi editior
Top Forums UNIX for Dummies Questions & Answers coming out from vi editior Post 302643487 by Scott on Saturday 19th of May 2012 01:57:13 PM
Old 05-19-2012
Do you have a free USB port? This works for me...

Image

You must really start reading man pages and start to make an effort to figure these things out.
These 4 Users Gave Thanks to Scott For This Post:
 

4 More Discussions You Might Find Interesting

1. Red Hat

Sendmail help on RH 9 - going out but NOT coming in..

Is there not one of us who can help here?? I'm really letting down my pants here - not sure what's going on but if you could foreward this link to a group you may know I would greatly appreciate it. I'm getting this error: May 30 22:18:35 MYSERVERNAME sendmail: j4V2HWka015549: ... (1 Reply)
Discussion started by: angelohl
1 Replies

2. Emergency UNIX and Linux Support

syslog not coming up

Hi All, I have a whole root zone, tsesbd02-zesbx01. On this zone, syslog service is not coming up. While it is working good on Global zone. Below are commands from tsesbd02-zesbx01 root@tsesbd02-zesbx01:/# svcs -a svc:/system/system-log:default svcs: -a ignored when used with arguments.... (13 Replies)
Discussion started by: solaris_1977
13 Replies

3. UNIX for Dummies Questions & Answers

VI editior line numbers

Hello All, I am very sure this a dumb question to many, but from my view its worth asking. When I do a vi on a file, on the right bottom side I am seeing something like below: 27,16-24 7% which tells me that I am on line 27 (which is the first number before the comma, i would like... (11 Replies)
Discussion started by: babyPen1985
11 Replies

4. Infrastructure Monitoring

Notifications not coming through

Issue: I'm not receiving notifications I can succesfully receive an e-mail if I do this on the command line: /usr/bin/mail -s "NAGIOS HOST ALERT on $HOSTNAME$" rgouette@butlerbros.com but, my command.cfg configuration below, refuses to send an e-mail when I set a service to a critical... (3 Replies)
Discussion started by: rgouette
3 Replies
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)
All times are GMT -4. The time now is 06:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy