<p dir="ltr">Sorry, I have re-read your first mail and you said it's mode is 755.</p>
<p dir="ltr">Don't know, it should work. Can you post the strace here or is it too verbose?</p>
<div class="gmail_quote">El 02/08/2013 01:28, "Xabier Oneca -- xOneca" <<a href="mailto:xoneca%2Bicecast@gmail.com">xoneca+icecast@gmail.com</a>> escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Has the script the executable bit set?</p>
<div class="gmail_quote">El 02/08/2013 01:23, "Phil - w2lie" <<a href="mailto:w2lie@w2lie.net" target="_blank">w2lie@w2lie.net</a>> escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hi All, thanks for the replies so far..<br>
I will try to address as many of them as I can in a group reply:<br>
<br>
Xabier Oneca -- xOneca wrote:<br>
Just to confirm, are you sure the scripts' path in config file is
relative to the chroot directory?<br>
<br>
<br>
- Yes, I am working under the new path names in my xml file. The
Web, Admin, and Log directories all work as planned. The shell
files are in the same path.<br>
<br>
Jeff, I believe that answers your question as well. <br>
<br>
<br>
</div>
"Thomas B. Rücker" wrote:<br>
<pre>I guess you mean chown and chroot?
Or just chown, but no chroot?
<i><span>/</span>if<span>/</span></i> I read this correctly, then this would mean, that it tries to run
connect.sh in the root directory of your chroot, so /connect.sh and when
seen from outside <i><span>/</span>home<span>/</span></i><user>/icecast/connect.sh
Are there any security features on this system, that might interfere?
SELinux? AppArmor?
If all else fails, try to run this instead:
strace icecast -c <i><span>/</span>home<span>/</span></i><user><i><span>/</span>icecast<span>/</span></i><config>.xml
==
- I was running both options, chroot and chown/grp. I first ran under a chown/chgrp config in my xml. I then added in the chroot flag to see if that had helped. I don't think I gained any ground, because when I try and chroot from shell, I see this:
[~]# chroot /home/<user>/icecast
chroot: cannot run command `/bin/bash': No such file or directory
So let's just assume I should crawl before I can run. From here on out I guess I'll leave chroot flag at 0
My chroot directory was setup as /home/<user>/icecast The scripts are in /home/<user>/icecast so in my xml I just reference /connect.sh as the script to run (no path). When I don't chroot, I call script /home/<user>/icecast/connect.sh and that still can't be located. Yet, running a find ~ -name connect.sh from the user's account shows the full path just fine.
SELinux is disabled. I don't believe I am running AppArmor. This is a CentOS VPS (which I probably should have stated earlier).
I ran the strace. It is well over my head. If I capture it to a file, would you be willing to look it over for me? I'm no linux noob, but I'm no where near being an expert either.
</pre>
Thank you all for the help so far.. <br>
Phil<br>
</div>
<br>_______________________________________________<br>
Icecast mailing list<br>
<a href="mailto:Icecast@xiph.org" target="_blank">Icecast@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/icecast" target="_blank">http://lists.xiph.org/mailman/listinfo/icecast</a><br>
<br></blockquote></div>
</blockquote></div>