01-14-2013
if you have a lifetime warranty... you can use it for life... but i would say a 10 years lifespan is what you can expect.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello everyone, I was searching for locations where I can get End of Life information on multiple versions of Unix.
I have found some information which I list below, what I have not found or confirmed is where I can get the information for:
DEC Unix/OSF1 V4.0D
NCR Unix SVR4 MP-RAS Rel 3.02.... (2 Replies)
Discussion started by: robertmcol
2 Replies
2. Solaris
Hello, I'm trying to fix this server System Board (CPU/Memory Unit). The error indicates that its missing 3.3VDC. So far all the fuses and caps have been checked. I new at this type of machine, need help for idea on this system. Thank you in advance.
Vu (0 Replies)
Discussion started by: vhtran
0 Replies
3. Solaris
Hi all ,
I am trying to install solaris 9 on E2900 that is connect to a 3320 SCSI storage , The issue is that i want to have the SCSI disks(3320) to start with controllers 1 and 2 ( c1t0 ....c2t0) and my 2 local disks on c3 and c4 .
Is there a way that i could accomplish that ...
Thanks... (3 Replies)
Discussion started by: ppass
3 Replies
4. Solaris
Hi men,
Have you ever meet this error ?
I install full Sun MC 4.0 packages (+ Add ons) exception of Sun Midrange Platform Administration because i don't know how to configure it
Then all other servers are ok, only E2900 servers have Config reader module error: Data Acquisition error
I... (12 Replies)
Discussion started by: tien86
12 Replies
5. Solaris
Dear Friends,
Sun Fire E2900 crashed. I collected explorer output. core dump files been generated.
There some interesting output files related to crash dumps, that I need some help from you guys to understand.
The file in the explorer output is under /sysconfig/crash it's called:... (5 Replies)
Discussion started by: Sun Fire
5 Replies
6. Solaris
Hi,
I am fairly new to Solaris , i have an e2900 server which gives the following output on the console:
Fri Sep 23 08:20:57 noname.example.com lom: /N0/SB0 : F
ailed AR interconnect test. Status = 00060040
Fri Sep 23 08:21:00 noname.example.com lom: AR Intercon
nect test: System board... (7 Replies)
Discussion started by: steve_b72
7 Replies
7. Emergency UNIX and Linux Support
Hi,
I have a scheduled activity to reboot E2900 server. But suddenly I came to know that console ip is not pinging, not connecting via telnet, as it used to connect. I already checked with my onsite person and he changed cable, still no luck. Network person checked his switch, which is showing... (8 Replies)
Discussion started by: solaris_1977
8 Replies
8. Solaris
While trying to perform a firmware upgrade on this ilom, the system refused to allow uploading of more than ~900k or so... We tried multiple approaches using FTP and all failed. I decided to start this morning by firing up Apache on another box and trying the same process via HTTP but when I went... (8 Replies)
Discussion started by: DustinT
8 Replies
9. Solaris
several newbie questions:
> how-to find serialnumber for Sun E2900
prtdiag -v does not show chassis serial number
> LOM is not connectable .
Are there any tools to get automatically Serial numbers for HW.
Thanks ! (7 Replies)
Discussion started by: magedfawzy
7 Replies
KCM(8) BSD System Manager's Manual KCM(8)
NAME
kcm -- is a process based credential cache for Kerberos tickets.
SYNOPSIS
kcm [--cache-name=cachename] [-c file | --config-file=file] [-g group | --group=group] [--max-request=size] [--disallow-getting-krbtgt]
[--detach] [-h | --help] [-k principal | --system-principal=principal] [-l time | --lifetime=time] [-m mode | --mode=mode]
[-n | --no-name-constraints] [-r time | --renewable-life=time] [-s path | --socket-path=path] [--door-path=path] [-S principal |
--server=principal] [-t keytab | --keytab=keytab] [-u user | --user=user] [-v | --version]
DESCRIPTION
kcm is a process based credential cache. To use it, set the KRB5CCNAME enviroment variable to 'KCM:uid' or add the stanza
[libdefaults]
default_cc_name = KCM:%{uid}
to the /etc/krb5.conf configuration file and make sure kcm is started in the system startup files.
The kcm daemon can hold the credentials for all users in the system. Access control is done with Unix-like permissions. The daemon checks
the access on all operations based on the uid and gid of the user. The tickets are renewed as long as is permitted by the KDC's policy.
The kcm daemon can also keep a SYSTEM credential that server processes can use to access services. One example of usage might be an nss_ldap
module that quickly needs to get credentials and doesn't want to renew the ticket itself.
Supported options:
--cache-name=cachename
system cache name
-c file, --config-file=file
location of config file
-g group, --group=group
system cache group
--max-request=size
max size for a kcm-request
--disallow-getting-krbtgt
disallow extracting any krbtgt from the kcm daemon.
--detach
detach from console
-h, --help
-k principal, --system-principal=principal
system principal name
-l time, --lifetime=time
lifetime of system tickets
-m mode, --mode=mode
octal mode of system cache
-n, --no-name-constraints
disable credentials cache name constraints
-r time, --renewable-life=time
renewable lifetime of system tickets
-s path, --socket-path=path
path to kcm domain socket
--door-path=path
path to kcm door socket
-S principal, --server=principal
server to get system ticket for
-t keytab, --keytab=keytab
system keytab name
-u user, --user=user
system cache owner
-v, --version
BSD
May 29, 2005 BSD