Displaying 20 results from an estimated 100000 matches similar to: "Different User"
2004 Aug 06
3
Different User
Hi All,
Hey there is no reason to run icecast as root. So the easy thing is just
not run icecast as root. In fact why are you running as root to begin
with??
On Mon, 23 Apr 2001, Steve Smith wrote:
> "Tweaker" == Tweaker <tweaker@yahoo.com> writes:
> > Is there a way that I can have icecast run as a different user other
> > than root?
>
> I'm
2004 Aug 06
1
Different User
On Mon, 23 Apr 2001, Steve Smith wrote:
> "harvey" == harvey smith <harvey@buskers.org> writes:
> > Hi All, Hey there is no reason to run icecast as root. So the easy
> > thing is just not run icecast as root. In fact why are you running
> > as root to begin with??
>
> If icecast is run from startup scripts on boot then it will almost
> certainly be
2004 Aug 06
2
Placing Icecast in a chroot jail
On Thu, 2002-12-19 at 01:30, msmith@labyrinth.net.au wrote:
> Alan Silvester <mascdman@shaw.ca> said:
>
> > Hi,
> >
> > (Sorry for the long email)
> >
> > As a bit of a learning exercise, I'm trying to place the icecast daemon
> > in a chroot jail. I've been mostly sucessful: I can get icecast to
> > serve the default stream from
2004 Aug 06
2
Placing Icecast in a chroot jail
Hi,
(Sorry for the long email)
As a bit of a learning exercise, I'm trying to place the icecast daemon
in a chroot jail. I've been mostly sucessful: I can get icecast to
serve the default stream from its jail, however I can't get multiple
streams to work.
I think the problem is that icecast can't resolve addresses in the jail,
however I do have an etc/hosts file and
2004 Aug 06
6
icecast on port 80 NOT as root
This may seem simple but I've looked all over and come up with nothing.
I'm interested in running Icecast 1.3.12 on port 80 to get around the
firewall issue. Obviously it's not prudent to run Icecast at root so I'm
wondering is there any way to safely run Icecast on port 80 using either
setuid or port redirection? Has anyone accomplished this and if so,
how'd you do it?
2004 Aug 06
2
pthread_cancel error
Hello,
I get the following error when I kill icecast. I am running icecast2 from
source on a debian unstable box. I have looked around google and tried a
couple of suggestions like moving and linking the libgcc library around,
without any luck.
"libgcc_s.so.1 must be installed for pthread_cancel to work?"
Anyone have any suggestions?
Thanks,
Alex Martin
shorewall@rettc.com
2004 Aug 06
1
pthread_cancel error
Ok. Sounds good. You are suggesting that icecast cannot find the
libgcc_s.so.1 file? Do you know how i can figure out what path icecast is
searching? Or how I can modify it? I tried moving the lib around the icecast
root without luck.
Or do I not understand what you have told me? Maybe you are suggesting it is
a debian related bug?
Thanks,
Alex Martin
http://www.rettc.com
----- Original
2004 Aug 06
2
YP submission / cURL issue. (icecast 2.0.1 / gentoo)
Yupp, same results. What else can be trying? Perms all seems a-ok, the name
resolution issue makes me feel funny. Here's a URL to the ptrace -f of the
non-chrooted run -- http://tinyurl.com/ytsqv ..
Although, MIRACULOUSLY, non-chrooted, non-privlidged, port 8000, + DNS works?!
Eventhough, without DNS it doesnt. As you can see! --
[2004-05-26 17:10:25] INFO main/main Icecast 2.0.0 server
2004 Aug 06
2
YP submission / cURL issue. (icecast 2.0.1 / gentoo)
Odd:
I just pulled SVN and compiled.. Wonderful new logging code, btw!
Now, why in the WORLD would the resolution be failling?! nsswitch.conf /
resolv.conf / hosts is all fine.. *shrug*
I can obviously put IPs instead of hosts in the URLs, however things still
fail..
-- Chris Pickert
ldd output--
ldd ./icecast
libcurl.so.2 => /usr/lib/libcurl.so.2 (0x4001f000)
2004 Sep 15
3
FW: Tip: using icecast in chroot mode may break timestamp inaccess.log
Please post to the mailing list the next time Ralf.
I'm not using yp directory listings, but I can guess why it is not working.
You're probably missing the libcurl.so library in your chroot jail
directories. Here's the listing of files I have in the chroot jail:
-----%< cut here
> ls -R
.:
admin etc lib opt usr var web
./admin:
listclients.xsl listmounts.xsl
2004 Aug 06
7
YP submission / cURL issue. (icecast 2.0.1 / gentoo)
Hello All:
I'm having troubles getting my YP submissions to go up correctly,
unfortunately there's not much I've been able to find. I'm getting NACK back
from the yp_add call, I've tried two different versions of cURL/libcURL on my
gentoo box to see if it was that, no luck. I've also replicated the problem
onto another gentoo box of mine and the exact same NACK/no
2004 Aug 06
7
YP submission / cURL issue. (icecast 2.0.1 / gentoo)
Hello All:
I'm having troubles getting my YP submissions to go up correctly,
unfortunately there's not much I've been able to find. I'm getting NACK back
from the yp_add call, I've tried two different versions of cURL/libcURL on my
gentoo box to see if it was that, no luck. I've also replicated the problem
onto another gentoo box of mine and the exact same NACK/no
2005 Jan 22
5
EROR: no DNS
[2005-01-22 23:31:17] EROR yp/send_to_yp connection to http://dir.xiph.org/cgi-bin/yp-cgi failed with "Couldn't resolve host 'dir.xiph.org'"
[2005-01-22 23:31:17] EROR yp/send_to_yp connection to http://www.oddsock.org/cgi-bin/yp-cgi failed with "Couldn't resolve host 'www.oddsock.org'"
This happens in chroot. Out of chroot, no problems. So I did the
2006 Sep 08
2
URL authentication
Does your instance of icecast have CURL support compiled in? Without it
authentication doesn't work I think. Furthermore, if you're running
icecast in a chroot jail then you need to make sure the curl shared
libraries are installed in the chroot jail as well.
Regards,
KJ
Peter Bengtson wrote:
> The icecast server isn't on a Mac, it just connects to a Mac for the
>
2011 Jun 03
1
Icecast authentication cant resolve address on Debian
Hi,
I am trying to use the url authentication method but am having trouble
getting icecast to work on a Debian installation on a VPS platform.
I have logged in my VPS as root and installed icecast using
apt-get install icecast2
setup the config file and then set ENABLE=true in /etc/init.d/icecast2
This initialy didn't work as it couldn't access log files and then had
trouble with the
2004 Oct 05
1
Bug, if you combine yp-dir-listing and chroot
Hi out there,
I just compiled the latest icecast2 and tried to use chroot and
yp-dir-listing together, but it doesn't work. Yp-dir-listing itself works
fine. I use a SuSE 8.2 and older libs (curl 7.10, libogg and lib vorbis
araound 1.0.95) that should still be in the combatibility-range, as far as
I can read on icecasts homepage. I hope there will be a fix for that bug
in the
2004 Aug 06
3
icecast 2.0.0 chroot problem
Thanks for the superfast reaction.
You got me started thinking.
I got rid of the following lines number 3 and 8 hereunder. They were
present in the example xml and I think that they don't belong here
because icecast won't run if chroot is not being used........
Now it starts. I am very happy about this!!!! :-)
JK
1 <security>
2 <chroot>0</chroot>
3
2015 Jun 03
2
Icecast URL authentication problem
System: Icecast 2.4.1 and 2.4.2, OS: CentOS 6.6 x64
Tried to install icecast using following two different methods described in these links:
(1) http://www.ukhost4u.co.uk/blog/538/install-icecast-2-centos-6-server/
(2) https://www.servint.net/university/article/taking-the-chill-out-of-installing-icecast/
Both of these resulted in working and stable icecast, but without the possibility of url
2004 Aug 06
2
icecast 2.0.0 chroot problem
Hello,
I seem to have a problem getting icecast 2.0.0 to start. I get the
following message:
[root@fels icecast]# /usr/local/bin/icecast -c
/usr/local/bin/icecast.xml
WARNING: You should not run icecast2 as root
Use the changeowner directive in the config file
I have not tampered with the default "security" section of the xml.
<security>
2004 Aug 06
1
icecast 2.0.0 chroot problem
Not sure if this has been fully answered yet, but in order for chroot
services to run effectively you will need to change the ownership of all
directories and files to, in this case, nobody:nobody. If you are not very
familar with running chroots, you will also need to disable the shell login
within your /etc/passwd file ex like this:
icecast:x:504:505::/opt/icecast:/sbin/nologin
In this case I