2 out of 6 found this review helpful:
File-Defrag
(0.03)
File-Defrag
(0.03)
PUBLIC SERVICE ANNOUNCEMENT!!!
Don't use any modules by Marc Lehmann, you will almost certainly regret it later. This author has a history of extreme hostility towards the Perl community and will actively prevent you from using his software if he doesn't like you, or what you do with it.
To give you an example, in the 6.1 release of AnyEvent he made AnyEvent.pm die if you use it together with IO::Async::Loop::AnyEvent. metacpan.org/source/MLEHMANN/AnyEvent...
See also this P5P thread for a little more context. www.nntp.perl.org/group/perl.perl5.po...
PSA Perl - 2012-04-24T07:23:31
Was this review helpful to you?
Yes
No
0 out of 1 found this review helpful:
File-Defrag
(0.03)
File-Defrag
(0.03)
It works for me (no EA).
I ran it on the root-partition ~60GB (~57GB used), ext3 on my notebook.
oesi - 2005-05-05T18:28:05
Was this review helpful to you?
Yes
No
2 out of 2 found this review helpful:
File-Defrag
(0.03)
File-Defrag
(0.03)
The lack of any documentation for something as low-level and critical makes me not want to use this.
From a quick look at the XS source code it looks like it's Linux-only. If so, Linux::Defrag would be a better name.
All the interesting code is in the bin/defrag script: why aren't they in the module instead? It would be useful to have a module with a single defrag_file() function for instance.
The defrag_files() function to defrag all files uses a homegrown directory traversing scheme instead of File::Find.
I would expect a good defragmentation scheme would do a bit of analysis to see which files needed defragmenting (based on how fragmented files were, how often they are accessed or how critical they are, etc.). This version doesn't seem to do any of that.
Robert Rothenberg - 2005-05-03T11:33:43
Was this review helpful to you?
Yes
No
