Blog 1: Lem - Warren Buffett walked into a University of Florida classroom in 1998 ... [2098423133938356224] (1).mp4 | (Open) | (Share)
▲ Previous | Next ▼/Projects/Consult
(Last modified: September 12 2026 16:44:43)Blog 2: Sam Stoffel - Jack Dorsey's simple rule for success in business [2089319019065057280].mp4 | (Open) | (Share)
▲ Previous | Next ▼/Videos
(Last modified: August 19 2026 10:40:22)Simple rule
Blog 3: Peter-Steinberger-What-Happens-When-4.7-_1786407922546.md | (Open) | (Share)
▲ Previous | Next ▼/Uploads
(Last modified: August 11 2026 02:25:23)Peter Steinberger: What Happens When 4.7 Million People Let It Cook - YouTube
Blog 4: Monitor_server_action____.md | (Open) | (Share)
▲ Previous | Next ▼/Dev/Helpful
(Last modified: April 06 2025 01:37:40)Monitor server action !!!
nohup inotifywait -mr -e move,delete,create /var/www/vhosts/domain.com/httpdocs >> /var/log/inotify_changes.log 2>&1 &
#example
nohup inotifywait -mr -e move,delete,create /var/www/vhosts/domain.com/httpdocs >> /var/www/vhosts/domain.com//logs/inotify_changes.log 2>&1 &
#see status
ps aux | grep inotifywait
# quick loook at ids
pgrep -af inotifywait
#any sh running?
ps -ef | grep -E "[^/]*/[^ ]*\.sh"
#or
ps aux | grep -E "\.sh($| )"
Reducing the number of directories being watched (or combining watches smartly) is often the best way to avoid:
- hitting the
max_user_watcheslimit - memory pressure or slowdown
- silent failures (like the one you just had)
✅ Tips for Keeping it Stable
Here are some best practices moving forward:
1. Be precise with paths
Watch only what's necessary:
inotifywait -mr /var/www/vhosts/example.com/httpdocs/uploads
2. Exclude heavy subdirectories
If you must watch a root dir but want to skip certain subfolders:
find /your/path -type d ! -path "*/node_modules*" ! -path "*/cache*" -print | \
xargs inotifywait -mr
3. Batch watches into fewer instances
Instead of:
inotifywait -mr /site1
inotifywait -mr /site2
inotifywait -mr /site3
You can often do:
inotifywait -mr /site1 /site2 /site3
4. Use --exclude for file types or patterns
inotifywait -mr --exclude '(\.log|\.tmp)$' /var/www
Perfect — that confirms it! 🎯
Reducing the number of directories being watched (or combining watches smartly) is often the best way to avoid:
- hitting the
max_user_watcheslimit - memory pressure or slowdown
- silent failures (like the one you just had)
✅ Tips for Keeping it Stable
Here are some best practices moving forward:
1. Be precise with paths
Watch only what's necessary:
inotifywait -mr /var/www/vhosts/example.com/httpdocs/uploads
2. Exclude heavy subdirectories
If you must watch a root dir but want to skip certain subfolders:
find /your/path -type d ! -path "*/node_modules*" ! -path "*/cache*" -print | \
xargs inotifywait -mr
3. Batch watches into fewer instances
Instead of:
inotifywait -mr /site1
inotifywait -mr /site2
inotifywait -mr /site3
You can often do:
inotifywait -mr /site1 /site2 /site3
4. Use --exclude for file types or patterns
inotifywait -mr --exclude '(\.log|\.tmp)$' /var/www
Blog 5: Disk_and_RAID_testing_commands.md | (Open) | (Share)
▲ Previous/Dev/Linux/Server Admin
(Last modified: July 31 2026 15:05:28)Disk and RAID testing commands
List physical disks:
lsblk -d -o NAME,MODEL,SERIAL,SIZE,TRAN
Show full SMART data:
sudo smartctl -a /dev/sda
sudo smartctl -a /dev/sdb
Show only the most relevant SMART values:
sudo smartctl -A /dev/sda | grep -iE 'Power_On_Hours|Power_Cycle|Reallocated|Pending|Uncorrectable|Wear|Host_Writes|Temperature|CRC'
Check overall SMART health:
sudo smartctl -H /dev/sda
sudo smartctl -H /dev/sdb
Run a short self-test:
sudo smartctl -t short /dev/sda
Then view the result after the stated wait time:
sudo smartctl -l selftest /dev/sda
Check RAID status:
cat /proc/mdstat
For RAID 1, [UU] means both disks are active.
Show detailed RAID information:
sudo mdadm --detail /dev/md0
Check configured RAID alert address:
grep -vE '^\s*(#|$)' /etc/mdadm/mdadm.conf
Send a harmless test alert:
sudo mdadm --monitor --scan --test --oneshot