Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'This "hint" is ludicrous' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
This "hint" is ludicrous
Authored by: readparse on Sep 25, '03 12:08:40PM

Thanks for the constructive criticism (well, at least inflammatory criticism). I'm the author of the hint, and you might have noticed my disclaimers about how there was probably a better way to do this. I think I specifically mentioned that calling perl from a shell pipeline wasn't the greatest way to go about it. I think I also mentioned the danger of killing "find" processes on a multi-user machine. I disclaimed and disclaimed some more.

I think I also asked for improvements. The first comment I saw in response was exactly that... "killall updatedb", which made me smile because I figured it probably worked and I was again guilty of overkill and embarassment. However, it happens to be 12:03, so updatedb is running right this second, and I just tried "sudo killall updatedb" and it didn't work. This makes me think that perhaps I had tried that approach earlier and it was one of many that did not work.

I also tried the renice approach, which was also suggested. I tried all of these things long before I finally wrote this script, which does exactly what I need. Yes, Perl is huge, and yet, this is not what I would call a "best practice". But this is something that just takes a moment to run, and it does exactly what I need. After having used it for many weeks with great success, I decided to share it with other users, that they might have similar success. Responses like yours are what keep people from sharing their ideas. It's not "ludicrous". It's "improvable".

Thanks anyway,
ReadParse



[ Reply to This | # ]