I was under the impression icecast wrote useage statistics to that directory, and you accessed them via http://host:port/admin/ Where does the xslt file come from that it tries to access when you attempt to access the admin page? Michael Smith wrote:>On Thursday 21 October 2004 05:36, Richard Morey wrote: > > >>I have just gotten a stream working and it is very cool. I am using >>ices0.4 to stream mp3s to icecast2 under redhat 9. I have a couple of >>questions, though: >> >>1. No files are being written to the admin directory. It is successfully >>writing the access and error logs and the pid file. The path is correct >>in the icecast.xml file. The user has write access to the admin >>directory. Do I need to turn something on? >> >> > >No, icecast will never write anything to the admin directory. > > > >>2. Also, no files are being written to the web directory. Same situation >>as above. >> >> > >Why would it? Again, icecast won't write here. > >The only places icecast will ever write to are: > - the log files > - the pid file (if configured) > - stream dump files (if configured). > >Sounds to me like everything is working correctly. > > > >>3. With ices0.4, is there any way to force ices to change the mp3 that >>it is playing while it is running in the background? I'd like to set up >>somekind of request system. Is there a script that does this? >> >> > >Can't help you with this one, I don't use ices 0.4. > >Mike > > > >
On Thursday 21 October 2004 12:16, Richard Morey wrote:> I was under the impression icecast wrote useage statistics to that > directory, and you accessed them via http://host:port/admin/Icecast serves various things (including usage statistics) from http://.../admin/... However, none of what it serves directly comes from files, it's all dynamically generated.> > Where does the xslt file come from that it tries to access when you > attempt to access the admin page?The XSLT files are in the admin directory. They never get written by icecast (they can be modified by the user though - to make it look different, or whatever else you might want to do). The XML that the XSLT is applied to is dynamically generated, icecast never writes an actual file for this. The response from the admin interface is the result of applying the XSLT transformation to the dynamically generated XML file. Mike
Ok, I think I see. The xslt files are kind of a template which tells icecast how to format the xml file that is the admin interface? Where can I get either an example xslt file or information on how this works? I didn't see details in the icecast docs. I have now skimmed the information on xml.com, but don't I need to know what xml tags icecast uses? Thanks for the help, Richard Michael Smith wrote:>On Thursday 21 October 2004 12:16, Richard Morey wrote: > > >>I was under the impression icecast wrote useage statistics to that >>directory, and you accessed them via http://host:port/admin/ >> >> > >Icecast serves various things (including usage statistics) from >http://.../admin/... >However, none of what it serves directly comes from files, it's all >dynamically generated. > > > >>Where does the xslt file come from that it tries to access when you >>attempt to access the admin page? >> >> > >The XSLT files are in the admin directory. They never get written by icecast >(they can be modified by the user though - to make it look different, or >whatever else you might want to do). > >The XML that the XSLT is applied to is dynamically generated, icecast never >writes an actual file for this. > >The response from the admin interface is the result of applying the XSLT >transformation to the dynamically generated XML file. > >Mike > > > >