I'd better have a look at what sort of memory DIMMs do I have installed on my netbook, which I have conveniently installed with Fedora 15.
Simply issue: dmidecode -t memory or dmidecode -t 17 (specifically on the memory module)
[shahmatd@beluga ~]$ sudo dmidecode --type 17
# dmidecode 2.11
SMBIOS 2.6 present.
Handle 0x000B, DMI type 17, 28 bytes
Memory Device
Array Handle: 0x000A
Error Information Handle: 0x000C
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: SODIMM
Set: None
Locator: DIMM1
Bank Locator: BANK 0
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: Hynix
Serial Number: 4784BE5200
Asset Tag: Unknown
Part Number: HMP112S6NFR8C-S6
Rank: Unknown
Ramblin' Dude
Wednesday, March 14, 2012
me teeth arr' aching
ahoy me mateys
had me teeth filled with fillins that me hates as me teeth still aches, arrr..
Friday, December 16, 2011
Solaris: Rotating the pacct file
If you happen to have the process accounting (pacct) enabled and the pacct, found under /var/adm to be growing stupendously. You can have it rotated, by means of:
/usr/lib/acct/turnacct switch
This will rename the pacct file to pacct.X, where X is a decimal digit
Or added into cron to rotate at desired interval, daily at midnight for example:
0 0 * * * /usr/sbin/logadm -p now rotate_pacct
Lastly, by mean of logadm, which I'm not covering here, because I'm lazy
/usr/lib/acct/turnacct switch
This will rename the pacct file to pacct.X, where X is a decimal digit
Or added into cron to rotate at desired interval, daily at midnight for example:
0 0 * * * /usr/sbin/logadm -p now rotate_pacct
Lastly, by mean of logadm, which I'm not covering here, because I'm lazy
Labels:
my techie notes,
pacct,
process accounting,
solaris
Friday, November 25, 2011
Solaris: Useful ok prompt (OBP) commands
The boot process can be aborted, if you are at the terminal, the abort sequences are Stop-A, L1-A or Break (depending on keyboard type), which can be emulated over remote consoles (rsc, alom, ilom, xscf)
Entering the following commands would obviously have consequences, and they are:
boot - boots to multi user mode
boot cdrom - boots from cdrom
boot -r - reconfiguration boot
boot -a - interactive reboot
boot -s - single user mode
Labels:
my techie notes,
OBP,
OBP boot commands,
OBP commands,
solaris
Solaris: init runlevels
Run levels are basically the operating mode that the Solaris OS will boot to after initiation.
Run levels that are available on the Solaris OS:
init 0 - power down, and drops to the OBP (Open Boot Prompt a.k.a. the ok> prompt)
init S/s - single user mode, used for maintenance or for troubleshooting
init 1 - administrative state, all file systems are mounted and local logins are allowed
init 2 - multi user, all daemons running except for nfs - nfs exports are not allowed
init 3 - multi user, this is where the Solaris OS goes live
init 4 - unused alternative multi users, unused unless defined
init 5 - power down - shuts down the OS and automatically power off if it is supported
init 6 - reboot
Run levels that are available on the Solaris OS:
init 0 - power down, and drops to the OBP (Open Boot Prompt a.k.a. the ok> prompt)
init S/s - single user mode, used for maintenance or for troubleshooting
init 1 - administrative state, all file systems are mounted and local logins are allowed
init 2 - multi user, all daemons running except for nfs - nfs exports are not allowed
init 3 - multi user, this is where the Solaris OS goes live
init 4 - unused alternative multi users, unused unless defined
init 5 - power down - shuts down the OS and automatically power off if it is supported
init 6 - reboot
Labels:
my techie notes,
runleves,
solaris,
solaris runlevels,
unix runlevels
Tuesday, November 8, 2011
Solaris: Checking which process is bound to which TCP/UDP port number
On solaris, you'll need lsof, but it seems that lsof is not part of the Solaris default installables. It should be available on Sunfreeware
# /usr/local/bin/lsof -i:123
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
xntpd 335 root 19u IPv4 0x600282a2c40 0t0 UDP *:ntp
xntpd 335 root 20u IPv4 0x600282a2840 0t0 UDP localhost:ntp
xntpd 335 root 21u IPv4 0x6002cb81ac0 0t0 UDP scglob20:ntp
xntpd 448 root 19u IPv4 0x30016a2c800 0t0 UDP *:ntp
xntpd 448 root 20u IPv4 0x6002f088500 0t0 UDP localhost:ntp
xntpd 448 root 21u IPv4 0x30016a2ca00 0t0 UDP 161.19.6.146:ntp
Else, you can do the following, the pid the following command could return multiple results
# port=25
# for i in `ls /proc`; do
> pfiles $i | grep AF_INET | grep "$port" 2>&1 >/dev/null; portfound=$?
> if [ $portfound -eq 0 ]; then
> echo "pid $i found to be bounded to port $port"
> fi
>done
pid 17175 found
pid 2874 found
pid 29348 found
pid 4482 found
pid 463 found
pid 6696 found
This can be followed with, use the pid output from the earlier output
# ps -eo user,pid,comm | grep
e.g.
# ps -eo user,pid,comm | grep 17175
root 17175 /usr/lib/sendmail
AIX: Checking which process is bound to which TCP/UDP port number
Had no idea what so ever at all on how to do this at first, Linux has a very convenient way of doing this. Say if you want to find out which process is bound to port 8080.
# netstat -Aan | grep 8080
f1000200031b6b98 tcp4 0 0 *.8080 *.* LISTEN
# rmsock f1000200031b6b98 tcpcb
The socket 0x31b6808 is being held by proccess 1306834 (httpd).
# netstat -Aan | grep 8080
f1000200031b6b98 tcp4 0 0 *.8080 *.* LISTEN
# rmsock f1000200031b6b98 tcpcb
The socket 0x31b6808 is being held by proccess 1306834 (httpd).
Subscribe to:
Posts (Atom)