![]() CrashPlanEngine however is important it's the main daemon file. I don't have an X server or libraries on my Nexenta install, so I'm uninterested in CrashPlanDesktop. I believe the crashplan service will create it.ĬrashPlan* are all shell wrappers for Java applications *.lsb (LSB for Linux Standard Base) are the original versions (I think I renamed them to this). I'm not sure why it's in the crashplan directory rather than somewhere like /var/run, but it is. This install tree is almost complete it can be put in /usr/local/crashplan (that's where I have mine) or wherever you like, so long as the configuration bits are also hooked up appropriately.ĬrashPlanEngine.pid is just the pidfile, a text file containing the process id of the currently running instance. Here's a rough difference between the two (listing.curr is my actual install, listing is extracted from the installer): Now this looks very close to the root listing of my actual current CrashPlan install on Nexenta, and by and large it is. testīin conf doc jniwrap.lic lang lib libjniwrap.so libjniwrap64.so libjtux.so libjtu圆4.so log skin upgrade Test: ASCII cpio archive (pre-SVR4 or odc)Ī cpio archive! I extracted that too, but in a separate directory: $ mkdir t cd t cpio -i. So it's a gzipped file! I decompressed it, and tested the result: $ gunzip test I didn't know what the big CrashPlan*.cpi file was, so I checked: $ file CrashPlan_.cpiĬrashPlan_.cpi: gzip compressed data, was "CrashPlan_.cpi", from Unix, max compression $ cd CrashPlan-install # the dir it extractedĬrashPlan_.cpi EULA.txt INSTALL README install.sh scripts uninstall.sh That's a gzipped tar archive, so I extracted it: $ tar xzf CrashPlan_Linux.tgz I went to the CrashPlan Linux download web page, and started downloading the installer in a scratch folder (this was the URL at the time of writing): $ wget It's a process of hacking things together, though, not a blind recipe that's why I'm proceeding almost as if it's a debugging session.Īnyhow, once we have a JRE installed (from apt-get above), we can try and extract out the guts of the Linux installer, so rather than running its install.sh, we can set it up manually. Of course, that won't work it needs the Nexenta JRE (but I get the whole JDK, as you never know when you'll need to brew up some Java): $ sudo apt-get install sun-java6-jdkĪnyhow, I received some comments and emails about setting all this up, and figured I'd break it down a little more for people who still want to get it all working. However, it seems that CrashPlan have changed their Linux installer's modus operandi, and it tries to install a (Linux) JRE of its own. I wrote an earlier post about installing CrashPlan on Nexenta.
0 Comments
Leave a Reply. |