Crunch qutting one me. (error code 2)

[Nazagul]

Is "N0hUX-R>YZ#.txt" the file name, the last line in the file, or the output on the screen?

If it's a filename I'm 99% sure the greater than character is what's causing the problem (maybe the number sign too), but since greater than is used for output redirection on the command line it's my guess.

that is the name of the last file it outputted. I couldn't open the file, and since I assumed the name is of the first and last part of output text, (according to what crunch said) that SHOULD be the last line in the file.

[TAPE]

I think we are on the right track in finding what the problem is, basically the filename appears
to give errors when attempting to write to disk due to the characters in the filename.

Regarding reading the file, if based on trying to read that file on a windows system,
try using LTFViewer http://www.swiftgear.com/ltfviewer/features.html

[TAPE]

that is the name of the last file it outputted. I couldn't open the file, and since I assumed the name is of the first and last part of output text, (according to what crunch said) that SHOULD be the last line in the file.

If you still have the files on your system ..

Can you try to in any case get the head & tail of the file START and of the last file created ?


And a ;

ls -lhrt

[Nazagul]

If you still have the files on your system ..

Can you try to in any case get the head & tail of the file START and of the last file created ?


And a ;

ls -lhrt

will try to do. Should have results on that sometime soon.

[bofh28]

will try to do. Should have results on that sometime soon.

Any results?

I have tried
./crunch 1 5 -f charset.lst lalpha-numeric-all-space -b 2gib -o START
because I didn't feel like waiting and all 5 files were created:

-rw-r--r-- 1 root root 2.0G Mar 30 19:41 a-o.xop.txt
-rw-r--r-- 1 root root 2.0G Mar 30 19:46 o.xoq-4~:2{.txt
-rw-r--r-- 1 root root 2.0G Mar 30 19:52 4~:2}--!y*y.txt
-rw-r--r-- 1 root root 2.0G Mar 30 19:58 -!y*z-<v;\>.txt
-rw-r--r-- 1 root root 867M Mar 30 20:01 <v;\,-     .txt

I will try your exact command when I get a few hours.

[Nazagul]

Thank you, I've been really busy

[bofh28]

I was able to recreate the problem and it looks like the problem is the / in the new filename. It probably just needs escaping with a \. I will see what I can do tomorrow. I wonder what other characters might need escaping.....

[TAPE]

@bofh28

Can any of the numerous crunch enthousiasts here help out with tests / trials
that you may have in mind ?

[bofh28]

The problem is / character in the filename. In Linux the / character is hardwired and cannot be used in a filename. So I am replacing the / (forward slash) with the unicode character 0x2044. I have started a new test and should take 2 hours to complete if successful.