search for: laika

Hello, We are searching for a possibility of "aliassing without wasting bandwidth". It is described in the following section which we found at http://open4all.info/ossa/_Icecast_Streaming_Server. # What happens is that when a listeners connects to your server and # requests the /laika stream, then your icecast server will connect # as a client to my machine, and then feed my stream to the listener. # All subsequent requests for /laika will use the same feed (i.e only # one connect will be made to my machine). Icecast will automagically # shut the link from my machine down when n...

...thout problem with the originating # stream on a cable modem or whatever. # In icecast 1.3.0 and above, we make this procedure much simpler. # If you want to relay a stream from another server, simply add an # alias for that server. Say you want to relay the broadcast originating # from my machine (laika.linux.tm:8000/laika), on your machine, do this: # alias laika http://laika.linux.tm:8000/laika # What happens is that when a listeners connects to your server and # requests the /laika stream, then your icecast server will connect # as a client to my machine, and then feed my stream to the listener...

...hout problem with the originating # stream on a cable modem or whatever. # In icecast 1.3.0 and above, we make this procedure much simpler. # If you want to relay a stream from another server, simply add an # alias for that server. Say you want to relay the broadcast originating # from my machine (laika.linux.tm:8000/laika), on your machine, do this: # alias laika http://laika.linux.tm:8000/laika # What happens is that when a listeners connects to your server and # requests the /laika stream, then your icecast server will connect # as a client to my machine, and then feed my stream to the listener...

David Dennis wrote: > welcome to the list. > > Check the archives. > > There you will find about one newbie a month minimum discovering that the > widely distributed and still available shout package version 0.8.0 > is actually deprecated and highly broken in exactly the manner you > describe. > > Thanks but one point I can make is I get the same results when not

...hout problem with the originating # stream on a cable modem or whatever. # In icecast 1.3.0 and above, we make this procedure much simpler. # If you want to relay a stream from another server, simply add an # alias for that server. Say you want to relay the broadcast originating # from my machine (laika.linux.tm:8000/laika), on your machine, do this: # alias laika http://laika.linux.tm:8000/laika # What happens is that when a listeners connects to your server and # requests the /laika stream, then your icecast server will connect # as a client to my machine, and then feed my stream to the listener...

...ER "Arcade Fire" TITLE "Funeral" FILE "Arcade Fire - 01 - Neighborhood #1 (Tunnels).flac" WAVE TRACK 01 AUDIO TITLE "Neighborhood #1 (Tunnels)" PERFORMER "Arcade Fire" INDEX 01 00:00:00 TRACK 02 AUDIO TITLE "Neighborhood #2 (Laika)" PERFORMER "Arcade Fire" INDEX 00 04:48:16 FILE "Arcade Fire - 02 - Neighborhood #2 (Laika).flac" WAVE INDEX 01 00:00:00 TRACK 03 AUDIO TITLE "Une Ann?e Sans Lumiere" PERFORMER "Arcade Fire" INDEX 00 03:29:61 FILE "Arcade...

...ger a different command (bar) if c1 and c3 are defined, but c2 is not. How would this look in puppet? For those of you familiar with cfengine, this would be similar to: c1.c2.c3:: foo c1.!c2.c3:: bar Thanks. Nathan T. Dabney Senior System Administrator, Infrastructure LAIKA, Inc.

.... After hours of investigation I can provide the following diagnostics: (1) The cron job hangs as does its sendmail child to which it pipes its output to; that is, ps -x gives this 1331 ? S 0:00 /USR/SBIN/CRON 1333 ? S 0:00 /usr/sbin/sendmail -FCronDaemon -odi -oem admin@laika.zup.bln.de (2) When I copy the command line from the above ps output and execute the command interactively within the shell, sendmail terminates properly and the mail arrives as expected. (3) When I do a killall sendmail, I get *weird* output in /var/log/mail: Jul 24 19:49:46 lola sendmail[1333]...

Hi all, I''m new to this list (and pretty new to backgroundrb). I''d like to jump in with a question, I hope you don''t mind. I''m trying to get my site working with backgroundrb to sent mail. It''s pretty basic stuff and I got it working pretty fast on my local machine (os x leopard). Unfortunately, when I try to deploy to my production machine I

Hi, I am using a small network of, say, 10 W2K workstations on which I run a database application using shared table and index files on a Samba 2.2.2 server (Suse Linux 7.2). The application was just ported from Clipper to XBase++. The Clipper compiled app (it's a 16-bit DOS application) runs fine. The 32-bit XBase++ app produces corrupt index files and behaves eratically after several

I''m having some problems with getting the drb server to work correctly on my production server. As a workaround I tried disabling automatic indexing and have a cron job manually update the index every hour or so. I disabled the automatic indexing with: def ferret_enabled? false end But whenever I try Page.rebuild_index I get a ''wrong number of arguments''

Hi, I''m using acts_as_ferret in with a mongrel and I'' m getting locking errors that after a while result in a corrupt database. I know about the problem with different processes writing to the index but I haven''t been able to get the DRB server working properly yet. I read on this list that another solution is to set :auto_flush to true but I''m not