search for: base_directori

On Thursday, 15 April 2004 at 08:07, Kristoffer R. Munroe wrote: > I am using the http protocol now and I still get the same results. <snip> > >DEBUG: Sending following information to libshout: > >DEBUG: Stream: 0 > >DEBUG: Host: 127.0.0.1:8000 (protocol: xaudiocast) According to the log file you attached, you're still using xaudiocast. Double check your

I see that I don't understand why it is still using the xaudiocast protocol here is my config file located in this same directory. <?xml version="1.0"?> <ices:Configuration xmlns:ices="http://www.icecast.org/projects/ices"> <ices:Playlist> <ices:File>test.txt</ices:File>

Hi all, I''d like to specify a base_directory and a list of directories (as variables that may be pulled via hiera later) that will be created under that base directory. base_dir = "/home/base" bars = ["a", "b", "c"] bars will be used to create the folders under base and also part of the information going into building a template so I

I'm no expert on Ices0.3 but that config doesn't look right to me. I'm guessing that it's imperative to have the server config as part of the stream section since you can have multiple streams from one source going to multiple destinations (I think anyways.. :) Take a look at my config for ices0.3 below : --------------------------------------------------- <?xml

On Thu, 15 Apr 2004, Kristoffer R. Munroe wrote: > I see that I don't understand why it is still using the xaudiocast protocol <SNIP> > [root@wyatt icecast]# ices -m mymp3stream -c ices.conf > Unknown Node: Server > Unknown Execution keyword: Base_Directory hmmm. Just before we go any further, are you using Ices 0.3 with libshout 2.0? Older versions will not work with

Well I think that I see where the problem is.. That is exactly right. [root@wyatt icecast]# ices -c /home/icecast/ices.conf Unknown Node: Server Unknown Execution keyword: Base_Directory <p>I dont think that ices is actually using the settings in the Server section of the config file. That would explain why the passwords are different. <p>So I guess that I will try to set it up

Hi, I''m using puppet 2.7.3 on RHEL/CentOS and I have an issue which is now a big blocking issue within my environment. What I''m trying to accomplish wit puppet is a create a mountpoint, mount a filesystem on it and install an application on that filesystems are set proper user/ group and permissions on it, but it fails big time. The issues I currently run into are about 3

Kristoffer R. Munroe wrote: > <ices:Password>hackme</ices:Password> > DEBUG: Mount: /mymp3stream, Password: letmein Are these not significant? -- Tim Schuh Ugly Networks --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to

I am trying to connect to an icecast2 server that I have running on redhat 9. Via Ice0. Here are the errors that I am getting. Any help would be greatly appreciated. Kris. <p>[root@wyatt icecast]# ices -m mymp3stream -c ices.conf -P hackme Unknown Node: Server Unknown Execution keyword: Base_Directory Logfile opened DEBUG: Sending following information to libshout: DEBUG: Stream: 0

Hi, I've been doing some work on ices, and I'd like to put out a release shortly so I can get to work on MultiStreaming (tm). Some bugs are fixed (eg now ices:BaseDirectory works (but note it is no longer called ices:Base_Directory - I figured since it was broken odds were good no one was using it), and song length is correct in the cue file), but mostly I've done a ton of work on the

Hi, I've been doing some work on ices, and I'd like to put out a release shortly so I can get to work on MultiStreaming (tm). Some bugs are fixed (eg now ices:BaseDirectory works (but note it is no longer called ices:Base_Directory - I figured since it was broken odds were good no one was using it), and song length is correct in the cue file), but mostly I've done a ton of work on the

I am using the http protocol now and I still get the same results. Does the mount point in ices need to be a directory that I am mounting to with read write permissions? Or is it a virtual mountpoint? <p>At 12:06 AM 4/15/2004, you wrote: >I am trying to connect to an icecast2 server that I have running on redhat 9. > >Via Ice0. Here are the errors that I am getting. >

In your Ices0. config file you need to change the protocol to work with Icecast 2 (at the moment you have it set up for Icecast 1.3 server). HTTP is the required protocol for connecting to Icecast 2. -------------------------------------- <Protocol>http</Protocol> -------------------------------------- <p>This should solve your immediate problem. <p>Joe.

The mountpoint is created by the Icecast server after initiated by Ices and only exists while it's source does. <p>Check the error.log in the Icecast 2 directorys to see why the Ices is having trouble making a connection. <p>>From: "Kristoffer R. Munroe" <krism@ragemp3.com> >Reply-To: icecast@xiph.org >To: icecast@xiph.org >Subject: Re: [icecast]

Here''s one for you! We''re rolling out some zip files to our servers using Puppet, there''s an exec that unzips them, the zip file is then deleted. I need to remove the old versions of the unzipped directory using Puppet when we rol out a newer version. So, on my client/node machine I have the below directories. /opt/1234 /opt/12345 /opt/123456 What I need to do, is

Dear Samba users, I am trying to update our local samba packages to 3.0.28. They are built against heimdal-1.0.1 and openldap-2.3.38. The Redhat Enterprise Linux 3 and 4 packages are working fine so far in my limited testing. The problem with heimdal and "net ads join..." has been fixed on all 3 platforms. On the Solaris 8 server, the "net ads join..." works correctly and the