On Thu, 2024-04-18 at 12:16 +0200, Aaron Lauterer wrote:
> I am not sure how often we actually need that information as it can add
> quite a bit of additional lines in the report in larger machines with
> many memory slots.
Good point. So in this case we could simply compact the output by counting,
without loosing any information:
# dmidecode -t 16,17 | grep -P "^\t(Max[^:]*city|Size|Part)" | sed -Ez
"s/\n(\tP[^\n]*)/\1/g" | sort | uniq -c
1 Maximum Capacity: 2 TB
4 Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1
4 Size: No Module Installed
> It might be better to keep that command in a cheatsheet to ask for it if
> actually needed instead of polluting the report :)
>
> On 2024-04-18 11:16, Alexander Zeidler wrote:
> > * to see if a RAM upgrade is slot/capacity-wise possible
> > * to spot added/replaced RAM that may now be causing issues
> >
> > Maximum Capacity: 2 TB
> > Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1
> > Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1
> > Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1
> > Size: 16 GB Part Number: 18ASF2G72PZ-2G6D1
> > Size: No Module Installed
> > Size: No Module Installed
> > Size: No Module Installed
> > Size: No Module Installed
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
