Sponsored Content
Full Discussion: st_san_safe enabled
Operating Systems HP-UX st_san_safe enabled Post 302147132 by libchk on Sunday 25th of November 2007 06:03:16 AM
Old 11-25-2007
st_san_safe enabled

$ uname -a
HP-UX vfauh203 B.11.11 U 9000/800 486452371 unlimited-user license

SCSI TAPE: dev = 0xcd520000 Failed open - st_san_safe enabled ()

is there any tools i can run to further investigate this err0r i received from syslog.log ? im new to hp-ux thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Account creation Sudo enabled

Hi, how to create account with the following be cron enabled only accessible via sudo (1 Reply)
Discussion started by: vilves
1 Replies

2. IP Networking

how we can find whether net is enabled or not

how we can find whether net is enabled or not with out using ping is there anyway please guide me thanku ,in advance sree (1 Reply)
Discussion started by: phani_sree
1 Replies

3. UNIX for Dummies Questions & Answers

$home full? or quota enabled?

I'm having trouble setting up passwordless ssh; specifically - I can only setup 2 remote hosts because when I try to add another to my known_hosts file it just won't. More investigation reveals various errors relating to 'No space left on device'. There is plenty of free disk space; user quotas... (9 Replies)
Discussion started by: dan-e
9 Replies

4. UNIX for Dummies Questions & Answers

how to test whether is user is enabled on disabled in Radius

Hi i am having two linux machines M1 M2 ,where M1 is the main machine and the connector is M2 Radius services are installed in M2. i pulled M2 users which resides on /user/local/raddb/users to M1 .so that any changes made to user in M1 will be reflected in M2. now i am disabling a user from M1... (0 Replies)
Discussion started by: kalyankalyan
0 Replies

5. UNIX for Dummies Questions & Answers

know a particular user is disabled or enabled

Hi all, i had 500 users how can i know whether user is disabled or enabled Thanks, kalyan (8 Replies)
Discussion started by: kalyan212
8 Replies

6. Solaris

see if async i/o is enabled in Solaris 9

Hi guys. This may be a stupid question but I am trying to see if my Solaris 9 server has async i/o enabled... Is there a quick way to determine this? Thanks in advance. (1 Reply)
Discussion started by: jamie_collins
1 Replies

7. Solaris

doubt reg Hardware watchdog enabled

Hi, Please let me know what is hardware watchdog enabled which we get when the solaris host is booting .As per my knowledge its the one states that the POST is enabled. correct me if am wrong. (1 Reply)
Discussion started by: rogerben
1 Replies

8. Linux

Error: Encryption support not enabled

Hi when I run the following GET commad: ./snmpget -m ALL -M /data/net/naamab/snmp/snmp_mib/ -v 3 -a MD5 -l authPriv -u test1 -A welcome1 -x DES -X privpass 127.0.0.1 NOVELSAT-MODULATOR-MIB::nsModLineCMMode.0 -d I get the error: Encryption support not enabled. snmpget: USM encryption... (1 Reply)
Discussion started by: naamabm
1 Replies

9. Hardware

HP raid Controllers enabled but drives not detected

I'm getting this message using hpacucli in HP ProLiant BL460c G6. Raid controller is already enabled: # hpacucli HP Array Configuration Utility CLI 8.35-7.0 Detecting Controllers...Done. Type "help" for a list of supported commands. Type "exit" to close the console. => ctrl all show... (0 Replies)
Discussion started by: linuxgeek
0 Replies

10. AIX

Slow NFS when cio/dio enabled

Hi, I have a bit of a NFS problem on AiX 6.1 : When I set the mount to cio and dio - needed for a database app - Everything slows down. The following is copying 700mb, top one is a normal mount bottom one is a mount with the cio/dio option enabled : # ./a.sh Wed Jan 11 11:41:24 GMT 2012... (5 Replies)
Discussion started by: AJCG1976
5 Replies
allocate(1)							   User Commands						       allocate(1)

NAME
allocate - device allocation SYNOPSIS
allocate [-s] [-w] [-F] [-U uname] [-z zonename] device allocate [-s] [-w] [-F] [-U uname] [-z zonename] -g dev-type DESCRIPTION
The allocate utility manages the ownership of devices through its allocation mechanism. It ensures that each device is used by only one qualified user at a time. The device argument specifies the device to be manipulated. To preserve the integrity of the device's owner, the allocate operation is exe- cuted on all the device special files associated with that device. The default allocate operation allocates the device special files associated with device to the uid of the current process. Only authorized users may allocate a device. The required authorizations are specified in device_allocate(4). When the system is configured with Trusted Extensions, allocate runs the clean program for the device before it grants access to the caller to that device. For devices with removable media that have a mountable file system, allocate mounts the media if the caller chooses. OPTIONS
The following options are supported: -F device Force allocates either free or pre-allocated devices. This option is often used with the -U option to allocate/reallocate devices to a specific user. Only those users that have solaris.device.revoke authorization are allowed to use this option. -g dev-type Allocates devices with a device-type matching dev-type. The dev-type argument specifies the device type to be operated on. -s Silent. Suppresses any diagnostic output. -U uname Uses the user ID uname instead of the user ID of the current process when performing the allocate operation. Only a user with the solaris.device.revoke authorization is permitted to use this option. The following options are supported with Trusted Extensions: -w Runs the device cleaning program in a windowing environment. If a windowing version of the program exists, it is used. Oth- erwise, the standard version is run in a terminal window. -z zonename Allocates device to the zone specified by zonename. OPERANDS
The following operands are supported: device Specifies the name of the device to be allocated. EXIT STATUS
The following exit values are returned: 0 Successful completion. 20 No entry for the specified device. other value An error occurred. FILES
/etc/security/device_allocate /etc/security/device_maps /etc/security/dev/* /etc/security/lib/* ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The invocation is Uncommitted. The options are Uncommitted. The output is Not-an-Interface. SEE ALSO
deallocate(1), list_devices(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5) Controlling Access to Devices NOTES
The functionality described in this man page is available only if Solaris Auditing has been enabled. See bsmconv(1M) for more information. On systems configured with Trusted Extensions, the functionality is enabled by default. /etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment. SunOS 5.11 30 Apr 2008 allocate(1)
All times are GMT -4. The time now is 01:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy