headers
Dave Sill | 9 Jun 2008 18:54
Picon

Administrivia: Tru64-UNIX-Managers information and policy statement

EVERYONE WHO RECEIVES THIS MESSAGE HAD BETTER READ IT THOROUGHLY.

Tru64-UNIX-Managers Information and Rules

This message is a summary of the Tru64-UNIX-managers charter and rules.
Failure to adhere to these guidelines may result in severe chastisement by
the list maintainer and other list participants. Retain a copy of this
statement and refer to it before submitting messages to the list or the list
administrator.

Last modified: 2002-10-09                                                     |

  1. Send only HP Tru64 UNIX (formerly Compaq Tru64 UNIX (formerly            |
     Digital UNIX (formerly Digital OSF/1))) system management questions and  |
     summaries to tru64-unix-managers <at> ornl.gov. Include your return address in
     the body of your message so people can reply directly to you. Avoid MIME
     and HTML--many people can't read them.

  2. This list is not moderated! Every message that is sent to the list will
     be passed on to every member of the list (with a few small exceptions).

  3. This mailing list is managed by a utility called Majordomo. You can
     subscribe to the list by sending a message like:

           subscribe tru64-unix-managers

     to majordomo <at> ornl.gov.

     Likewise, if you want to remove yourself from the list, send the
     message:
(Continue reading)

Permalink | Reply | 0 comments |
headers
labelles | 18 Jun 2008 02:39
Favicon

Setup of SSH key logins - TRU64 to Red Hat Linux

Hello,

I have an issue that has me baffled. I am trying to setup SSH-key 
authentication between TRU64 V5.1B and Red Hat Enterprise Linux (RHEL4 
update6). I want the TRU64 box the authenticate via SSH-keys within a 
script TRU64 to RHEL4.

I understand the basic differences of the SSH versions:

    TRU64 --> SSH2
    RHEL4 --> SSH 

I can get the following to work:

    TRU64 to TRU64
    RHEL4 to RHEL4
    RHEL4 to TRU64

I cannot get TRU64 to authenticate to RHEL4. Anyone have any 
thoughts/ideas? Any help greatly appreciated.

Steve

Stephen L. LaBelle
Metropolitan State College of Denver
Senior System Administrator
Database Administration Team
labelles <at> mscd.edu
303-556-3644
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Galt | 24 Jun 2008 20:59
Picon

Summary: Restoring root fileset on 4.0d

Thanks to all who replied and sorry for taking so long to post the summary.

I still do not know why I was unable to re-create the domain (see 
original post below).

There is a renamefset command that was suggested, but since the 
system was running (only the clone backups were failing because the 
root fileset was mistakenly named "roottmp") I did not want to risk 
renaming the root filesystem in multiuser mode ( I was working 
remotely). I was concerned that it may not work on the root file 
system and that I may just corrupt something.

I used the vdump/vrestore process ( which I had used many times 
before to expand root partition space and worked well) to copy the 
original data for root, usr, and var to another disk (creating the 
root fileset correctly this time...) and then I had a tech onsite 
move the new disk into the scsi position of the original disk. All is 
working properly now.

Regards.
John

At 08:28 AM 5/23/2008, you wrote:
>Hello Managers,
>This is something I have done successfully before but for some reason
>it is failing today.
>
>I want to restore the root advfs filesystem on a 4.0d system. I did
>this successfully on the same system last month, however, when I did
>it last month, I mistakenly named the root advfs fileset "roottmp"
(Continue reading)

Permalink | Reply | 0 comments |

Gmane