7,129 reputation
21743
bio website
location Boston, MA
age
visits member for 5 years, 9 months
seen Nov 11 '14 at 7:54

Jul
17
comment Understanding colo pricing with respect to power needs
That 1A number seems pretty low. I measured a rackable with a pair of opteron 250 CPUs and 8gb of ram in it -- under load 2.5A/110v. I took out one of the CPUs (and 4gb of ram) and the power draw went down to 1.2A.
Jul
17
answered Why su to root instead of logging in as root?
Jul
17
revised Configure a Local DNS Resolver That Only Caches for a Short Period
added 352 characters in body
Jul
17
answered Configure a Local DNS Resolver That Only Caches for a Short Period
Jul
15
comment The perfect server room?
Well, maybe one per user...
Jul
14
revised What are the skills required for a deployment engineer for network monitoring product company?
added 8 characters in body
Jul
14
revised What are the skills required for a deployment engineer for network monitoring product company?
added 676 characters in body
Jul
14
revised What are the skills required for a deployment engineer for network monitoring product company?
added 164 characters in body
Jul
14
answered What are the skills required for a deployment engineer for network monitoring product company?
Jul
14
comment How to restore remote access to a RHEL system from expanded permissions set over the entire filesystem?
In what format do you keep your backups?
Jul
12
answered Best way to compare (diff) a full directory structure?
Jul
11
comment Exchange server replacement that runs on Linux
@scott: do you use it with just imap for email or do you also use it for calendering as well?
Jul
10
revised Determine Location of Inode Usage
added 828 characters in body
Jul
10
answered Faster IMAP searching for Courier IMAP server on Linux
Jul
10
comment Determine Location of Inode Usage
That would likely take a billion years. A quicker thing to do is to run lsof | grep DIR and look in each of those directories for lots of new files.
Jul
10
comment Determine Location of Inode Usage
The inodes could also be taken by really deep directories, which this won't find. There are a number of weird edge cases in this, but the most common situation is a directory full of files with normal names.
Jul
10
comment Determine Location of Inode Usage
@mike G: You're 100% correct about this not being the fastest way to do this sort of thing. In my mind, the correct way to optimize this is to redirect to stderr when starting and finishing the "count directory entries" part of the script. That way, when you hit a directory with a million entries it will say "processing directory spool/postfix/maildrop" and then not say instantly "finished" and boom -- look in spool/postfix/maildrop and you'll see lots of files.
Jul
10
comment Determine Location of Inode Usage
I just ran a test on a directory with a million files and ls took 22 seconds and echo * took 12 seconds. (For the record, echo * in shell won't hit the arg limit because echo in 99% of shells in active use is a built-in)
Jul
10
comment Determine Location of Inode Usage
True about the ls -- in situations like this I worry more about it being clear what I'm doing and not so much about the performance. I'm pretty sure that you can use echo $line/* | wc -w in place of ls $line | wc -l and you avoid the ls sorting issue.
Jul
10
revised Determine Location of Inode Usage
added 185 characters in body