Hackman -- A Hack Manager module for TivoWeb

[PortlandPaw]

From the blizzard-paralyzed northeast, here's the latest hackman beta. Please post comments, good experiences, bug reports, etc., as appropriate.

[SeanC]

No problems going from 3.3.11 to 3.3.12.

[ronsch]

I'm trying to install and run Hackman for the first time.

This 3.3.11 on a Philips HDR-31202 running 3.0 with Tivowebplus 1.0.
I think I have all the files in the right place with the correct permissions but this is what i'm getting:

Log cleared on Sun Jan 23, 2005 by TivoWeb
channelmap
favicon
hackman
CHILDSTATUS 434 126 /var/local/tivoweb-tcl/bin_ppc/find: /var/local/tivoweb-tcl/bin_ppc/find: cannot execute binary file
while executing
"exec $find / -path /proc -prune -o -path /dev -prune -o -path /tvlib -prune -o -path /tvbin -prune -o -path /etc -prune -o -name "tivoweb*" \! -name *..."
(file "/var/local/tivoweb-tcl/modules/hackman.itcl" line 3003)
invoked from within
"source $module "
index
info
lj_utils
logos
logs
mail
mfsbrowser
moviesearch
phone
resources
sched
screen
search
theme
ui
webremote
whatson
Accepting Connections
** end log**

The binaries all were set with chmod 755.

[vertigo235]

Originally posted by PortlandPaw
From the blizzard-paralyzed northeast, here's the latest hackman beta. Please post comments, good experiences, bug reports, etc., as appropriate.

Will this fix my problem? I'm still using 1.0 and it works for my needs. But I'd be willing to try it out if it will help you solve the problem I had?

[vertigo235]

OK so now I get this error

INTERNAL SERVER ERROR
--cut here--
action_hackman '/' ''
can't read "procs": no such variable
while executing
"string first $appname $procs"
(procedure "::action_hackman" line 84)
invoked from within
"::action_$action $chan $part $env"
("eval" body line 1)
invoked from within
"eval {::action_$action $chan $part $env}"
--cut here--

[PortlandPaw]

You must be using something more recent than 1.0 to see the error you're seeing but to answer your question, yes, I think the latest version would address that problem.

[PortlandPaw]

Originally posted by vertigo235
OK so now I get this error

INTERNAL SERVER ERROR
--cut here--
action_hackman '/' ''
can't read "procs": no such variable

Something's screwy, because two lines before this, procs is defined:
set procs "[exec /bin/bash -c "cat /proc/\[1-9\]*/stat"]"

I would remove and reinstall a fresh download of hackman and all related files.

[vertigo235]

I'm sorry, I wasn't more specific. I decided to go ahead and load the latest beta that you posted today, and the error I posted above if from that version.

[vertigo235]

One thing that did work this time is that it detected a bunch of stuff and told me about renaming things and how they would not be found or something. Then when I hit OK, I got these errors.

[stevel]

I tried the beta on my DSR704 and got:

hackman
CHILDSTATUS 2112 126 /var/local/tivoweb-tcl/bin_ppc/find: /var/local/tivoweb-tcl/bin_ppc/find: cannot execute binary file
    while executing
"exec $find / -path /proc -prune -o -path /dev -prune -o -path /tvlib -prune -o
 -path /tvbin -prune -o -name "tivoweb*" \! -name *.log -type d -print"
    (file "/var/local/tivoweb-tcl/modules/hackman.itcl" line 2992)
    invoked from within
"source $module "

Now why is it looking in bin_ppc?

[Throg]

I didn't have any problems with 3.3.12 at all. I'm ready for a final.

[PortlandPaw]

Originally posted by stevel
I tried the beta on my DSR704
Now why is it looking in bin_ppc?

It's trying to see if the ppc find works. If it does, fine. If not, it uses the mips version. I've used this error trap technique for the past few betas to select the proper find and sendkey files. Apparently, there's still a problem of some kind. Confusing, since it seems to be working for others. What beta version did you upgrade from?

[vertigo235]

dry deleting the ppc version...

[ronsch]

Should I also try deleting the ppc find? Or is it supposed to be using that one for a SA?

[vertigo235]

I'm pretty sure, ppc should be fore series 1, while mips is for series 2

[ronsch]

Can I substitute the standard "find" that is used in the other scripts?

[stevel]

Originally posted by PortlandPaw
What beta version did you upgrade from?

It wasn't a beta version, but maybe two of your releases earlier.

[PortlandPaw]

I don't know what all you guys are trying to do, but let me try to explain at least the philosophy here:

The hackman distribution includes two sub-directories, bin_mips and bin_ppc, which are meant to correspond to the same sub-directories in TivoWebPlus. They would have to be added to TivoWeb setups, but I recommend just switching to TivoWebPlus.

These sub-directories have two files each in them -- find and sendkey. The ppc versions are generally for Series 1, the mips for Series 2, but I've heard that there may be some overlap.

To determine which files to use, hackman tests one of them, the ppc version, and if it works that becomes the operational file. If it returns an error, then the other must be the right one.

This seems to be working for some people but not for all. But the best place to start is with the recommended installation.

[ronsch]

After work, I will double-check that I copied the correct version of "find" to the bin_ppc directory, however it seems the trap code isn't correctly trapping the error.

[PortlandPaw]

OK, here's what it's doing. It's trying the mips find to locate rc.sysinit, a file that should be on every TiVo:
exec $source_dir/bin_mips/find / -name rc.sysinit -type f

stevel, your Series 2 should accomplish that feat with no problem and use the mips find. I wonder if it's generating a different, perhaps acceptable error, that is kicking it into the ppc class. I think I'll put some debug code into the next beta to see what's happening.

ronsch, your Series 1 should choke on it (as mine does) and use the ppc find instead. It appears to select the ppc directory but gives an error message appropriate for the mips version. Therefore my suspicion that the finds are in the wrong places.

[PortlandPaw]

Originally posted by iguru42
Just installed 3.3.11 and got:

A path, pathname or startup conflict has been found... hackman found tnlited startup commands in /etc/rc.d/rc.sysinit
but found /sbin/tnlited in the file scan.
telnetpathname has been set to tnlited.

You may need to make adjustments if this conflict resolution was incorrect,
or resolve the multiple startup issues.

I don't see the conflict.

Telnet is in sbin

Telnet is being started by rc.sysinit, where is the conflict?

Oh and when telnet and ftp are being started from rc.sysinit is it normal for both of them to have yellow buttons?

I think the latest version should take care of your first observation and, yes, the button should be yellow if telnet or ftp is being started from rc.sysinit.

[PortlandPaw]

Originally posted by bdbax
I get this when I try to toggle on-screen clock any ideas? I am running hdvr2 with 4.0

INTERNAL SERVER ERROR
--cut here--
action_backdoorcodes '' 'set "backdoorcode" "6";'
tivo
couldn't execute "/devbin/sendkey": no such file or directory
while executing
"exec $env(TIVO_ROOT)/devbin/sendkey $evrc($key)"

Looks like you've got the wrong sendkey command (mips instead of ppc or vice versa). I'm still trying to figure this out, but in the meantime, try swapping the files in the bin_mips and bin_ppc directories. But if you try any of the new beta updates, be sure to completely reinstall all of the hackman files so we're all on the same page.

[SeanC]

Originally posted by PortlandPaw
I think the latest version should take care of your first observation and, yes, the button should be yellow if telnet or ftp is being started from rc.sysinit.

Ok, that explains that then. I didn't even know that tivoftpd was installed in var/hack until hackman told me. I now have telnet and ftp installed in sbin and being called from rc.sysinit.

Nuthin better than runnin a tight ship.

[beejaycee]

FWIW, I replaced the old Hackman I was running (3.3.9, I believe) with your latest beta (3.3.12) and no longer have the problem with "find" in /bin_ppc on my S2 DTivo. I don't know if it is because of something you did or something that was fixed when I ran e2fsck which repaired numerous errors but it's all good! Previously, I was copying the find file from /bin_mips to /bin_ppc to get hackman to run.

[ronsch]

All right.. We're making progress. I replaced both versions of find and sendkey in their respective folders. Still using 3.3.11

On Windows -
bin_mips find 12/5/04 132kb
bin_mips sendkey 8/6/04 556kb
bin_ppc find 10/28/04 73kb
bin_ppc sendkey 11/2/04 1kb

Upon trying a quick reload out of tivowebplus, my TiVo rebooted. After the boot completed and when Tivowebplus started running, Hackman was present and operational.

In all likelyhood, I screwed up over the weekend when copying in the find and sendkey binaries.

I just tested the "reload Tivowebplus" button and it worked without rebooting the TiVo so I guess that was a one-time thing. The text on the restart tivowebplus confirmation screen refers to restarting "tivoweb" and "wait until tivoweb 1.9.4 is loaded" as if I was stopping/starting Tivoweb instead of Tivowebplus.

[stevel]

I tried re-copying all of the bin_xxx files from the beta file, chmodded them all to 755, but still hackman complains about bin_ppc/find

I can run find from the bin_mips folder just fine. If I run the one in bin_ppc, I get the error "cannot execute binary file", as I would expect, and this is exactly the error that Hackman reports and then fails to load for.

[ronsch]

I actually spent some time watching some shows on my TiVo. When I came back to my PC, Tivowebplus was completely unresponsive. After a telnet initiated reboot everything was fine again.

Watching hackman go through the initial keystrokes on the TV was something else. When it was done, it ended up on channel 24 playing the live buffer in slow motion!

[PortlandPaw]

Originally posted by stevel
I tried re-copying all of the bin_xxx files from the beta file, chmodded them all to 755, but still hackman complains about bin_ppc/find

I can run find from the bin_mips folder just fine. If I run the one in bin_ppc, I get the error "cannot execute binary file", as I would expect, and this is exactly the error that Hackman reports and then fails to load for.

I have an idea -- I'll first check for Series 1/2 and select the appropriate mips/pcc find. But then I'll check it as I'm doing now -- if if doesn't work, I'll load the other version. Maybe this two step approach will work. I'm baffled how the current screening process works on some Series 2 but not on others.

[mulscully]

I jst installed hackman and it is not showing up in tivowebplus.. any ideas?

[PortlandPaw]

Please look at the ReadMe for troubleshooting hints and directions on how to report any startup errors.