When I attach a USB storage device to my Solaris server, the mount point is coming up as /rmdisk/unnamed_rmdisk
Is there anyway I can have this device come up as a mounted device with a predetermined mount name eg /morespace rather than unnamed_rmdisk ? (0 Replies)
When I attach a USB storage device to my Solaris server, the mount point is coming up as /rmdisk/unnamed_rmdisk
Is there anyway I can have this device come up as a mounted device with a predetermined mount name eg /morespace rather than unnamed_rmdisk ? (2 Replies)
hi, I was wondering if there's a way to safely disconnect a usb device from computer, I ask this because in windows when you disconnect a usb pen with the safe removal, the pen light then turns off, while I tried removing the pen with solaris and the light was still on ? (2 Replies)
Hello,
I need to run an application in wine that requires write permission to a USB device. Wine users must not have root privileges. On FreeBSD this could be accomplished by adding the user to the wheel group but I am using Debian 6.0. From looking at the passwd file it is not obvious what... (6 Replies)
In linux system when a pnp usb device is plugged in then how does the system gets a notification of it?
I mean to say in linux usb system there is usb host controller above which is host controller driver above which is usb core.
So does the host controller/usb core keeps on polling the usb bus... (1 Reply)
Hi all
unixware 7.1.3 I'm afraid ! I connected a usb tape drive and it was automatically recognised in the device list (sdiconfig -l) and created devices in /dev/rmt (ctape1 etc.). I could successfully read and write to the device.
Then unplugged the usb cable and plugged it back in again... (0 Replies)
Hi,
i am developing an application on an ARM 7 architatcure with a small Linux.
i want to run tar on a usb device (~10 Mb) but it runs realy slow. the command only takes 1% of cpu usage.
is there a way to improve the tar command or is the USB-Connection the bottleneck here? (4 Replies)
Discussion started by: louisk
4 Replies
LEARN ABOUT HPUX
st_san_safe
st_san_safe(5) OBSOLETED st_san_safe(5)NAME
st_san_safe - determine whether access to tape device special files without the no-rewind-on-close option is allowed (OBSOLETED)
VALUES
Failsafe
Default
Allowed values
Recommended values
or
DESCRIPTION
Note: this tunable is obsoleted and has been renamed to beginning with release HP-UX 11i v3.
This tunable notifies the tape driver whether it should allow access to device special files without the no-rewind-on-close option. When
this tunable is on the tape driver will fail any open on a tape device special file without the no-rewind-on-close option (that is, or with
a status of
The tunable allows the safe sharing of tape devices in SAN tape backup solution configurations. The disabling of device special files
without no-rewind-on-close in a SAN tape backup solution configuration prevents the accidental sending of a rewind command on close from
HP-UX systems via standard tape commands like which would corrupt a backup in process.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect immediately.
When Should the Tunable Be Turned On?
This tunable should be turned on if the system is going to be used in a SAN tape backup solution configuration.
What Are the Side Effects of Turning the Tunable On?
The tape driver will fail any open to a tape device special file that does not have the no-rewind-on-close option with a status of This
behavior prevents the usage of any tape device special file without the no-rewind-on-close option.
When Should the Tunable Be Turned Off?
This tunable should be turned off if the system is not part of a SAN tape backup solution configuration or the system utilizes will not
function unless it has access to device special files without the no-rewind-on-close option.
What Are the Side Effects of Turning the Tunable Off?
A rewind may be issued from this system accidentally on close possibly corrupting a backup being issued from another system on the SAN.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by Hewlett-Packard.
SEE ALSO norewind_close_disabled(5), scsi_tape(7), scsimgr_estape(7).
Tunable Kernel Parameters st_san_safe(5)