#1 added to directory on rmount DVD drive

Thread Tools Search this Thread
Operating Systems Solaris #1 added to directory on rmount DVD drive
# 1  
Old 03-09-2011
#1 added to directory on rmount DVD drive

Currently have an issue were we use a script to load a security .dat key. The script was failing to load stating "Unable to open directory". I ssh'd into the server and performed an ls -la on the /cdrom directory. I show the usual cdrom0 but the directory on the cd should be key but is showing key#1. I have put this same cd in other drives and the #1 doesn't show up.

I was able to work around this issue by performing a volmgt stop and start, after performing this, the /cdrom directory shows cdrom0, key and key#1. If I cd into key and ls I show key.dat file, and the key#1 directory is empty. I was able to delete the key#1 directory using rmdir and now my script will work to load the security dat key.

Now I have moved to the next disk in the line and the #1 issue has shown back up. I was able to perform the volmgt stop and start to work around again and have started checking each disk, and the issue shows up.

My question is, is this a cd formatting issue or is there something else at work here. This is on a 10 host system running nis+.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

AIX physical DVD/CD drive

Hello, I have some doubts about the dvd/cd physical on power machine and AIX. I see on my AIX lpar and see there is 1 DVD drive and its physical location bash-4.4# lsdev | grep cd0 cd0 Available 03-00-00 SATA DVD-RAM Drive bash-4.4# lscfg -vpl cd0 cd0 ... (12 Replies)
Discussion started by: Phat
12 Replies

2. UNIX for Dummies Questions & Answers

Mount the cd/dvd drive

Next, you will need to install the software package that provides DHCP services (a.k.a. the DHCP daemon software). It is located on the installation DVD ISO image for the CentOS Linux Distribution. Associate the (Disc 1 of 2) DVD ISO with the virtual machine's CD/DVD optical drive, create a... (1 Reply)
Discussion started by: beerpong1
1 Replies

3. Solaris

Solaris 10 install with no DVD drive

Hi Guys, I think i probably know the answer to this question, but ill put it out there. I have access to one, and only one SunFire v240 with no DVD drive. I have been tasked with installing Solaris 10 on there (Solaris 8 is on at the moment). The obvious thing was to try a USB DVD... (4 Replies)
Discussion started by: Sol-nova
4 Replies

4. AIX

dvd media in drive

Hello, It's some tool in AIX to check what kind of media (DVD+RW DVD-RW DVD-RAM) is inserted in drive? In linux there is very nice tool called dvd+rw-mediainfo. (0 Replies)
Discussion started by: vikus
0 Replies

5. UNIX for Dummies Questions & Answers

dvd in drive how to check

is there some tools(not graphical) command to reconnoiter what kind of cd/dvd is on drive (dvd+rw/dvd-rw/etc)? (1 Reply)
Discussion started by: vikus
1 Replies

6. Solaris

move DVD drive between domains in M5000

Hi, I 've a M5000 system with 2 domains configured on it. How can i move the DVD from one domain to the other ? so that i can access the drive in the second domain. cfgdevice -l does not work on M5000 (6 Replies)
Discussion started by: fugitive
6 Replies

7. Solaris

Sharing DVD Drive in LDoms Environment

I have T5220 server with DVD drive. I have installed few logical domains in the server and wonder how they can share the DVD drive. I have not seen any mention of that in Sun documentation. (7 Replies)
Discussion started by: StarSol
7 Replies

8. Solaris

external DVD-ROM drive for our datacentre

Hi there In our Data centre we have a mixture of SPARCS running from v100 and ultra10's to v800 and v1250 boxes we also have a large amount of x86 X2100 and X4100 boxes I am looking to purchase an external DVD-ROM drive that we can plug into the back of any of the boxes if we need to (I... (2 Replies)
Discussion started by: hcclnoodles
2 Replies

9. AIX

Check for media in DVD drive

I would like to check for the existance of media in a DVD drive prior to running a mkcd. Is this possible? I have accomplished this in the past with tctl, but that was with a tape drive. Any help is appreciated. Thanks (0 Replies)
Discussion started by: dmjoen
0 Replies

10. Solaris

DVD drive problem after upgrade to Solaris 10

After upgrading to solaris 10 (from sol 8) on a SUN Blade 1500, it seems that the dvd/cd-rom does not accept dvds nor cds in the dvd drive. After I insert a dvd/cd in the drive, the disk is simply ejected (!) Is it possible that the upgrade made the system not being able to recognize these... (2 Replies)
Discussion started by: miket
2 Replies
Login or Register to Ask a Question
SSH-COPY-ID(1)						    BSD General Commands Manual 					    SSH-COPY-ID(1)

ssh-copy-id -- use locally available keys to authorise logins on a remote machine SYNOPSIS
ssh-copy-id [-n] [-i [identity_file]] [-p port] [-o ssh_option] [user@]hostname ssh-copy-id -h | -? DESCRIPTION
ssh-copy-id is a script that uses ssh(1) to log into a remote machine (presumably using a login password, so password authentication should be enabled, unless you've done some clever use of multiple identities). It assembles a list of one or more fingerprints (as described below) and tries to log in with each key, to see if any of them are already installed (of course, if you are not using ssh-agent(1) this may result in you being repeatedly prompted for pass-phrases). It then assembles a list of those that failed to log in, and using ssh, enables logins with those keys on the remote server. By default it adds the keys by appending them to the remote user's ~/.ssh/authorized_keys (creating the file, and directory, if necessary). It is also capable of detecting if the remote system is a NetScreen, and using its 'set ssh pka-dsa key ...' command instead. The options are as follows: -i identity_file Use only the key(s) contained in identity_file (rather than looking for identities via ssh-add(1) or in the default_ID_file). If the filename does not end in .pub this is added. If the filename is omitted, the default_ID_file is used. Note that this can be used to ensure that the keys copied have the comment one prefers and/or extra options applied, by ensuring that the key file has these set as preferred before the copy is attempted. -n do a dry-run. Instead of installing keys on the remote system simply prints the key(s) that would have been installed. -h, -? Print Usage summary -p port, -o ssh_option These two options are simply passed through untouched, along with their argument, to allow one to set the port or other ssh(1) options, respectively. Rather than specifying these as command line options, it is often better to use (per-host) settings in ssh(1)'s configuration file: ssh_config(5). Default behaviour without -i, is to check if 'ssh-add -L' provides any output, and if so those keys are used. Note that this results in the comment on the key being the filename that was given to ssh-add(1) when the key was loaded into your ssh-agent(1) rather than the comment contained in that file, which is a bit of a shame. Otherwise, if ssh-add(1) provides no keys contents of the default_ID_file will be used. The default_ID_file is the most recent file that matches: ~/.ssh/id*.pub, (excluding those that match ~/.ssh/*-cert.pub) so if you create a key that is not the one you want ssh-copy-id to use, just use touch(1) on your preferred key's .pub file to reinstate it as the most recent. EXAMPLES
If you have already installed keys from one system on a lot of remote hosts, and you then create a new key, on a new client machine, say, it can be difficult to keep track of which systems on which you've installed the new key. One way of dealing with this is to load both the new key and old key(s) into your ssh-agent(1). Load the new key first, without the -c option, then load one or more old keys into the agent, possibly by ssh-ing to the client machine that has that old key, using the -A option to allow agent forwarding: user@newclient$ ssh-add user@newclient$ ssh -A old.client user@oldl$ ssh-add -c ... prompt for pass-phrase ... user@old$ logoff user@newclient$ ssh someserver now, if the new key is installed on the server, you'll be allowed in unprompted, whereas if you only have the old key(s) enabled, you'll be asked for confirmation, which is your cue to log back out and run user@newclient$ ssh-copy-id -i someserver The reason you might want to specify the -i option in this case is to ensure that the comment on the installed key is the one from the .pub file, rather than just the filename that was loaded into you agent. It also ensures that only the id you intended is installed, rather than all the keys that you have in your ssh-agent(1). Of course, you can specify another id, or use the contents of the ssh-agent(1) as you pre- fer. Having mentioned ssh-add(1)'s -c option, you might consider using this whenever using agent forwarding to avoid your key being hijacked, but it is much better to instead use ssh(1)'s ProxyCommand and -W option, to bounce through remote servers while always doing direct end-to-end authentication. This way the middle hop(s) don't get access to your ssh-agent(1). A web search for 'ssh proxycommand nc' should prove enlightening (N.B. the modern approach is to use the -W option, rather than nc(1)). ENVIRONMENT
SSH_COPY_ID_LEGACY If the SSH_COPY_ID_LEGACY environment variable is set, the ssh-copy-id is run in a legacy mode. In this mode, the ssh-copy-id doesn't check an existence of a private key and doesn't do remote checks of the remote server versions or if public keys are already installed. SEE ALSO
ssh(1), ssh-agent(1), sshd(8) BSD
June 17, 2010 BSD

Featured Tech Videos