I had commands for ;@WORK to turn off files,dirs and commands for khttpd... and all was well.

When I upgraded to v434 today for my Mk2, I started seeing "hijack config error" on my display.

So I plugged into a serial port again for debug to see:

Code:

---

[hijack] ERROR: "khttpd_dirs=0"
[hijack] ERROR: "khttpd_commands=0"
[hijack] ERROR: "khttpd_files=0"

---

Yet the FAQ still lists these commands as valid...

Did I miss something?

-Ben

upgraded from what prior version?

Those options vanished as of Hijack-v381, a very very long time ago.

See this thread for more info.

I got it - Thanks Mark... I looks at the FAQ's online for what options are included and I searched this website for something that might talk about the options that are now deprecated...

The FAQ still shows the old commands... guess its time for them to be removed...

The Website here, well, I guess I didn't search for the right thing (although I did enter various versions of the stuff in question).

Anyway - thanks!

-Ben

Ben you're right, but the Hijack kernal evolves so fast that it's really too hard tor anyone to keep it up to date. It does do a great job of getting someone familiar with the kernal however. Your best bet in situations like this is to just ask (like you did) or do a search.

God I suck. I really wish I had time to tackle an update to the hijack FAQ. it's just one of those things that once I start it I know it will take forever, and I don't wanna half ass it. Sorry for letting it get out of date in the first place folks!!!