Re: Consistent header structure corruption in sucker

Hello, local ml.

I'm sorry I didn't get to your mail earlier. As the README file states, "You
will need to create at least one .conf file for various YoSucker internal
reasons!". Nice try using /dev/null as a config file, but I guess YoSucker
won't find what it looks for in that location (and it woun't be able to create
various files it needs for its proper functionality as the names of those files
derive from the config file name). I guess that causes your problems. Create a
regular config file, retry and let me know if the problem persists.

I'm not saying it is impossible to find the right setup without using a config
file, but I've never tested such a possibility. I know it is not an ideal
situation. But the internal structure of YoSucker got so complicated it was
hard to implement the new features as they are. If I was to remove the .conf
file dependency, I am affraid I would get into to much unstable code, ie. mess.
I tried to recode YoSucker several times from scratch, but always felt like
re-inventing the same thing so I would always give up eventually. This was the
only possibility...

Now I checked your setup and it works fine for me. It is possible that your
connection gets time-out-ed and so you get the 'header corruption' message.
probably. try to remove sneakysleep. create reguler .conf file. even empty. let
me know.

Cheers.

Vlad
-z3r0-