Sponsored Content
Operating Systems Solaris VxVM..anything to worry about in here.. Post 302267686 by incredible on Saturday 13th of December 2008 09:58:14 AM
Old 12-13-2008
How can we conclude what's the problem?
I have the explorer from the system. So whatever outputs you want, I can provide the information. Kindly assist me out. Im stuck.
 

7 More Discussions You Might Find Interesting

1. Solaris

VxVM

All solaris rescue gurus out there .... I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory. The machine is (was) running Vxvm with the root volume encapsulated. I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies

2. Filesystems, Disks and Memory

vmstat -d with VxVM

I've got a Linux box that I'm pretty sure is having some disk issues. iostat isn't installed, but vmstat is, so i've been trying to use that to do some initial diagnostics while I go through our company's change control process to get iostat installed. The problem I'm having is that the disks... (4 Replies)
Discussion started by: kknigga
4 Replies

3. Solaris

VxVM on Solaris.

Hi, Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies

4. Solaris

Reg. VXVM

Hi Guys, I have a doubt either to Reboot the server after Replacing the disk0. I have two disks under vxvm root mirrored and i had a problem with primary disk so i replace the disk0 failed primary disk and then mirrored. After mirroring is it reboot required ? (7 Replies)
Discussion started by: kurva
7 Replies

5. Filesystems, Disks and Memory

VxVM and MPxIO

:confused: Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO. If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies

6. Solaris

No of volumes in vxvm

Anyone knows that how many volumes can be created in a Diskgroup? Thanks in advance... (1 Reply)
Discussion started by: bpsunadm
1 Replies

7. Solaris

vxvm

hi all, how can we check whether vxvm is installed in our system or not in solaris? Thanks in advance dinu (4 Replies)
Discussion started by: dinu
4 Replies
OPENSC-EXPLORER(1)						   OpenSC tools 						OPENSC-EXPLORER(1)

NAME
opensc-explorer - generic interactive utility for accessing smart card and similar security token functions SYNOPSIS
opensc-explorer [OPTIONS] DESCRIPTION
The opensc-explorer utility can be used interactively to perform miscellaneous operations such as exploring the contents of or sending arbitrary APDU commands to a smart card or similar security token. OPTIONS
The following are the command-line options for opensc-explorer. There are additional interactive commands available once it is running. --reader num, -r num Use the given reader number. The default is 0, the first reader in the system. --card-driver driver, -c driver Use the given card driver. The default is auto-detected. --mf path, -m path Select the file referenced by the given path on startup. The default is the path to the standard master file, 3F00. If path is empty (e.g. opensc-explorer --mf ""), then no file is explicitly selected. --wait, -w Wait for a card to be inserted --verbose, -v Causes opensc-explorer to be more verbose. Specify this flag several times to enable debug output in the opensc library. COMMANDS
The following commands are supported at the opensc-explorer interactive prompt. ls list all files in the current DF cd file-id change to another DF specified by file-id cat [file-id], cat sfi:sfi-id print the contents of the currently selected EF or the contents of a file specified by file-id or sfi-id. info [file-id] display attributes of a file specified by file-id. If file-id is not supplied, the attributes of the current file are printed. create file-id size create a new EF. file-id specifies the id number and size is the size of the new file. delete file-id remove the EF or DF specified by file-id rm file-id remove the EF or DF specified by file-id verify key-typekey-id [key] present a PIN or key to the card. Where key-type can be one of CHV, KEY or PRO. key-id is a number representing the key or PIN reference. key is the key or PIN to be verified in hex. If key is omitted, PIN will be verified with PIN-Pad. Example: verify CHV0 31:32:33:34:00:00:00:00 change CHVid [[old-pin] new-pin] change a PIN, where id is the PIN reference Examples: Change PIN: change CHV2 00:00:00:00:00:00 "foobar" Set PIN: change CHV2 "foobar" Change PIN with pinpad: change CHV2 put file-id input copy a local file to the card. The local file is specified by input while the card file is specified by file-id. get file-id [output] copy an EF to a local file. The local file is specified by output while the card file is specified by file-id. If output is ommited, the name of the output file will be derivated from the full card path to file-id. do_put hex-tag input update internal card's 'tagged' data. hex-tag is the tag of the card's data. input is the filename of the source file or the literal data presented as a sequence of hexadecimal values or '"' enclosed string. do_get hex-tag [output] copy the internal card's 'tagged' data into the local file. The local file is specified by output while the tag of the card's data is specified by hex-tag. If output is ommited, the name of the output file will be derivated from hex-tag. mkdir file-id size create a DF. file-id specifies the id number and size is the size of the new file. erase erase the card, if the card supports it. random count generate random sequence of count bytes. update_record file-id rec_nr rec_offs data update record specified by rec_nr of the file specified by file-id with the literal data data starting from offset specified by rec_offs. data can be supplied as a sequence of the hex values or as a '"' encolsed string. update_binary file-id offs data binary update of the file specified by file-id with the literal data data starting from offset specified by offs. data can be supplied as a sequence of the hex values or as a '"' encolsed string. debug [level] set OpenSC debug level to level. If level is ommited the current debug level will be shown. apdu hex_data send a custom APDU command hex_data. asn1 file-id parse and print the ASN1 encoded content of the file specified by file-id. quit exit the program. SEE ALSO
opensc-tool(1) opensc 06/03/2012 OPENSC-EXPLORER(1)
All times are GMT -4. The time now is 11:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy