[Libtorrent-devel] problem with rtorrentInit.sh
dpsenner at gmail.com
Wed May 26 08:36:23 UTC 2010
You're right. I could have thought of that earlier. :-D So I'm going to try
1) add LD_LIBRARY_PATH, PATH and LD_RUN_PATH to be logged into the logfile
This way I'll find out if there is a difference in these when I run it
manually or when it is being run by init.
2) if this yields nothing I'll test it without the bash profiles
3) if that gives me no clue I'll try out balaji's init script and give dtach
Thanks for the help!
> -----Original Message-----
> From: Charles Clark [mailto:cmc at stegosaur.us]
> Sent: Wednesday, May 26, 2010 10:01 AM
> To: Dominik Psenner
> Subject: Re: [Libtorrent-devel] problem with rtorrentInit.sh
> | From: Dominik Psenner <dpsenner at gmail.com>
> | I just revisited and put some more time into this, but still no results.
> | logfile is writable for everyone, so this is not the point of failure.
> | it just looks like if rtorrent or screen terminates after init. And
> still it
> | works fine if I start it manually. Pretty odd, isn't it?
> | Every little help would be appreciated, really.
> I don't have any debian based linux, but in general when unix
> startup scripts work by hand but not during startup the thing to
> look at is a) environment, and b) is there something that needs
> a tty or interactive mode to run?
> The environment is usually different in whatever means you use
> to get a root shell and in the startup environment used by init.
> The things that are likely to matter the most are the PATH, and
> any LD_LIBRARY_PATH or LD_RUN_PATH variables.
> If you get a root shell using "su -" that is usually pretty
> close to the startup environment. However, if you have root's
> bash startup files customized that might not be the case. If the
> PATH is not very short and if there are any LD_ variables set,
> then temporarily move aside .profile, .bashrc, and .bash_profile
> in ~root, do a new "su -" and try running it again.
> You can add a startup script that does something like "env >
> /root/startup_env" and nothing else really to empirically
> determine the startup environment if you can't figure out where
> it is set in what system config files using man pages, "info",
> and reading the startup scripts.
> I don't think that screen needs a tty to run in a startup
> script, and it will provide one for rtorrent, so I don't think
> that is the problem. More likely rtorrent isn't in your startup
> environment's path, or needs a library you are getting from
> LD_LIBRARY_PATH instead of having the directory listed in
> /etc/ld.so.conf (although this is much more likely if you
> compile rtorrent/libtorrent by hand than if you use any
> pre-built packages).
> Good luck.
> Charles Clark | cmc at stegosaur.us
More information about the Libtorrent-devel