03-29-2012
10 More Discussions You Might Find Interesting
1. Solaris
I have a very old sunOS 4.xx server on a SPARCstation 5. What is the command , if any, that is similar to prtdiag and prtconf?
Thanks (4 Replies)
Discussion started by: antalexi
4 Replies
2. UNIX for Dummies Questions & Answers
Hello all ,
This is the output of my prtdiag command ...The speed of each of the CPUs is listed below (1281 MHz ) ..That's fine ..I'm confused about the (System clock frequency: 183 MHZ ) ..What is the difference between System Clock freq and CPU freq ...THanks..
System Configuration: Sun... (5 Replies)
Discussion started by: luft
5 Replies
3. Solaris
Hello Guys, :confused:
I have tried Up to my Levels
pls help me if u know any solution
Pls look out the following O/P,
Log Messages
=================================================
SUN> pwd
/usr/platform/SUNW,Sun-Fire-V240/sbin
SUN>
SUN>
SUN> prtdiag -v
bash: prtdiag: command not... (7 Replies)
Discussion started by: sure.solaris
7 Replies
4. Solaris
hi,
we have an e6900 and my sys admin says that the number of processors and memory were reduced to 4 and 8GB. However, a prtdiag |grep Memory returns 16GB of memory. So what is my system's memory? psrinfo returns 4 online and 4 offline CPUs.
Thanks.
Kumar (1 Reply)
Discussion started by: kumar27
1 Replies
5. Solaris
Hi,
Recently installed a Firmware patch on T5120 (solaris 10,138888-03).
The patch installation was Success and system came up fine as well. My apps are running fine too.
Problem is prtdiag does not work as it used to earlier. the output is very different from other t5120s I have and... (1 Reply)
Discussion started by: upengan78
1 Replies
6. Solaris
Hi, a couple of T2000 servers did not show the component status and the output was too short. There was a patch that needed to be installed. I also updated to the latest recommended patch cluster and OBP patch.
After reboot/restart of picl, it worked ok for a couple of weeks. Then suddenly it went... (12 Replies)
Discussion started by: incredible
12 Replies
7. UNIX for Advanced & Expert Users
Dear All....Help required
prtdiag -v command shows no output on my V440 server.
Following is the details:
root@sdp16b>prtdiag -v
root@sdp16b>
root@sdp16b>uname -a
SunOS sdp16b 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-V440
root@sdp16b>echo $path
/usr/sbin /usr/bin /usr/sbin... (6 Replies)
Discussion started by: Junaid
6 Replies
8. UNIX for Dummies Questions & Answers
I am having trouble figuring this one out.....Is this a 2CPU or a 4CPU v490 with 16GB? I think it is a 2CPU system, looking for confirmation.
$ prtdiag
System Configuration: Sun Microsystems sun4u Sun Fire V490
System clock frequency: 150 MHz
Memory size: 16384 Megabytes
... (1 Reply)
Discussion started by: config_boy
1 Replies
9. Solaris
Hi. I have 2 SunFire V490 servers running Solaris 10. We may have to upgrade with more memory on one of them to make it compatible with the other. Here's the one with 12GB of RAM:
Memory size: 12288 Megabytes
========================= CPUs ===============================================
... (1 Reply)
Discussion started by: th1amigo
1 Replies
10. Solaris
selected lines from the output of the "prtdiag -v" command on a T5240 SUN server running Solaris 10.
Are the following known as FRU names and what do they mean?
MB/CMP0/BR0/CH0/D0
MB/CMP0/BR0/CH1/D0
SYS/FANBD0/FM0/F0
SYS/FANBD0/FM0/F1
SYS/MB/CMP0/BR1/CH0/D1 ... (1 Reply)
Discussion started by: snoman1
1 Replies
LEARN ABOUT OPENSOLARIS
systemd-cryptsetup-generator
SYSTEMD-CRYPTSETUP-GENERATOR(8) systemd-cryptsetup-generator SYSTEMD-CRYPTSETUP-GENERATOR(8)
NAME
systemd-cryptsetup-generator - Unit generator for /etc/crypttab
SYNOPSIS
/lib/systemd/system-generators/systemd-cryptsetup-generator
DESCRIPTION
systemd-cryptsetup-generator is a generator that translates /etc/crypttab into native systemd units early at boot and when configuration of
the system manager is reloaded. This will create systemd-cryptsetup@.service(8) units as necessary.
systemd-cryptsetup-generator implements systemd.generator(7).
KERNEL COMMAND LINE
systemd-cryptsetup-generator understands the following kernel command line parameters:
luks=, rd.luks=
Takes a boolean argument. Defaults to "yes". If "no", disables the generator entirely. rd.luks= is honored only by initial RAM disk
(initrd) while luks= is honored by both the main system and the initrd.
luks.crypttab=, rd.luks.crypttab=
Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any devices configured in /etc/crypttab
(luks.uuid= will still work however). rd.luks.crypttab= is honored only by initial RAM disk (initrd) while luks.crypttab= is honored
by both the main system and the initrd.
luks.uuid=, rd.luks.uuid=
Takes a LUKS superblock UUID as argument. This will activate the specified device as part of the boot process as if it was listed in
/etc/crypttab. This option may be specified more than once in order to set up multiple devices. rd.luks.uuid= is honored only by
initial RAM disk (initrd) while luks.uuid= is honored by both the main system and the initrd.
If /etc/crypttab contains entries with the same UUID, then the name, keyfile and options specified there will be used. Otherwise, the
device will have the name "luks-UUID".
If /etc/crypttab exists, only those UUIDs specified on the kernel command line will be activated in the initrd or the real root.
luks.name=, rd.luks.name=
Takes a LUKS super block UUID followed by an "=" and a name. This implies rd.luks.uuid= or luks.uuid= and will additionally make the
LUKS device given by the UUID appear under the provided name.
rd.luks.name= is honored only by initial RAM disk (initrd) while luks.name= is honored by both the main system and the initrd.
luks.options=, rd.luks.options=
Takes a LUKS super block UUID followed by an "=" and a string of options separated by commas as argument. This will override the
options for the given UUID.
If only a list of options, without an UUID, is specified, they apply to any UUIDs not specified elsewhere, and without an entry in
/etc/crypttab.
rd.luks.options= is honored only by initial RAM disk (initrd) while luks.options= is honored by both the main system and the initrd.
luks.key=, rd.luks.key=
Takes a password file name as argument or a LUKS super block UUID followed by a "=" and a password file name.
For those entries specified with rd.luks.uuid= or luks.uuid=, the password file will be set to the one specified by rd.luks.key= or
luks.key= of the corresponding UUID, or the password file that was specified without a UUID.
rd.luks.key= is honored only by initial RAM disk (initrd) while luks.key= is honored by both the main system and the initrd.
SEE ALSO
systemd(1), crypttab(5), systemd-cryptsetup@.service(8), cryptsetup(8), systemd-fstab-generator(8)
systemd 237 SYSTEMD-CRYPTSETUP-GENERATOR(8)