This is a redhat package. You would make my Christmas if you can tell me how to make this work on Ubuntu (Debian)
Quite a bump, but here it goes. :)
Today I took some effort in moving our backburner Manager from a Windows7 x64 PC to a linux machine running a x64 Debian installation. Things should be fairly identical on a Ubuntu x64 system, by now the most common Linux distro around (see http://www.phoronix.com/scan.php?page=news_item&px=MTA5MTQ).
The alien method didn’t work for me, as alien refuses to create x64 .deb from a x86 .rpm package. The other method however got me going. I pulled the mentioned dependencies and then some, unpacked the .rpm and moved files into their respective places (mainly the backburner software to /usr/discreet/* and the initscripts to /etc/init.d/*). To my surprise I was able to start the manager using the init script and connect to it using a Backburner monitor/server from one of our (Win7 x64) workstations. Furthermore I was able to clean the init scripts a bit by changing it to a bash script instead of a sh (mainly in support of ‘let’ and -lt arguments). Obviously, a lot of work is to be done to fully comply to current Debian/Ubuntu initscript guidelines, but so far I was already happy that at least it was running cleanly.
I did some quick test by submitting some jobs and all seemed fine until a bit later the backburner manager started to quit on me spitting segfaults (as seen in dmesg) on the way out:
[19951173.827364] backburnerManag: segfault at 0 ip 00000000f76dd041 sp 00000000f4b4c360 error 4 in libDLnrapi.so[f764d000+11a000]
[19958274.229959] backburnerManag: segfault at 68 ip 000000000810fcdc sp 00000000f2f8e198 error 6 in backburner Manager[8048000+fd000]
[19958649.419581] backburnerManag: segfault at 13 ip 0000000000000013 sp 00000000f4afb1cc error 14 in backburnerManager[8048000+fd000]
Without a proper error log it’s kind of hard resolving this type of crashes, so I think this pretty much ends the adventure.
I think Autodesk would do a good job in releasing a x64 .deb installation of at least the Backburner Manager as it would allow the manager to run properly on the currently most popular Linux distibutions.
Why go to all that trouble...instead just installing a Redhat clone (like CentOS or Scientific Linux)?
That being said I can’t seem to maintain a connection to more than three servers at a time so there is obviously something wrong with the way I am doing things.
Simple, backburner manager is not that much of a resource hog, so I tried installing it on one of our existing servers. It’s not like that you want to setup a dedicated box for that. Especially when you are not sure things will be working properly at all. ;-)