search for: passim

...G: Mount: /fs Dumpfile: (null) Logfile opened DEBUG: Initializing playlist handler... DEBUG: Initializing builting playlist handler... DEBUG: Randomizing playlist... Mounted on http://65.165.174.101:8000//fs DEBUG: Builtin playlist handler serving: /usr/local/icecast/freesound/Sciss/Azoiphon/Passim.mp3 DEBUG: ID3v1 song: Passim DEBUG: ID3v1 artist: Sciss DEBUG: Layer: III Version: MPEG-2 LSF Frequency: 22050 DEBUG: Bitrate: 32 kbit/s Padding: 0 Mode: single-ch DEBUG: Ext: 0 Mode_Ext: 0 Copyright: 0 Original: 0 DEBUG: Error Protection: 0 Emphasis: 0...

At 1:48 PM -0400 7/6/01, Brendan Cully wrote: >On Friday, 06 July 2001 at 10:32, tom erbe wrote: >> icecast 1.3.10 is the server i'm running, but its ices 0.1 that gives >> me a segfault under solaris. it works just fine on my linux box. ices > >The segfaults are a stack size problem. Try changing STACKSIZE near >the top of thread/thread.c from 8192 to 65536 or so...

...d both of those things. Everything looks normal, it is > just plowing through the songs at high speed. You might be able to > listen until you can't keep up at http://hagstrom.calarts.edu:8000 > > Here is the output I'm getting > /usr/local/icecast/freesound/Sciss/Azoiphon/Passim.mp3 > DEBUG: ID3v1 song: Passim > DEBUG: ID3v1 artist: Sciss > DEBUG: Layer: III Version: MPEG-2 LSF Frequency: 22050 > DEBUG: Bitrate: 32 kbit/s Padding: 0 Mode: single-ch > DEBUG: Ext: 0 Mode_Ext: 0 Copyright: 0 Original: 0 > DEBUG: Error Pr...

...eans is that nozero2.img is growing during the test (from 2048 to 4096 blocks). When I run the test locally this file stays at 2048 blocks the whole time, and the test does not fail. One other unfortunate problem is that Fedora is having lots of toolchain problems right now (see Fedora devel list passim) so we cannot really be sure that *any* other tool we are using has been built correctly :-( I've already disabled LTO in qemu and libguestfs, but possibly there are other toolchain bugs. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programm...

...filesystem koji is using may matter (for example, if this is something that shows up on btrfs but not ext4, that would explain why koji fails when I pass locally...) > > One other unfortunate problem is that Fedora is having lots of > toolchain problems right now (see Fedora devel list passim) so we > cannot really be sure that *any* other tool we are using has been > built correctly :-( I've already disabled LTO in qemu and libguestfs, > but possibly there are other toolchain bugs. > > Rich. > -- Eric Blake, Principal Software Engineer Red Hat, Inc....

...eed to deal with the pid or kill the > pid in the cleanup function. > > - As a result, cleanup functions are radically simpler, and often > disappear completely. > > - Also removed the comment "# The cleanup() function is called > implicitly on exit" passim partly because the cleanup functions > have mostly been removed and partly because it should be clear from > looking at functions.sh. > > There is one additional change: In the test-memory*.sh tests, nbdkit > used to run in the foreground, but that seems to be a consequence...

v1 was here: https://www.redhat.com/archives/libguestfs/2018-September/msg00057.html v2: - Fix tab vs spaces in configure.ac. - To generate list of plugins, use printf instead of xargs. - Use 'source ./functions.sh' instead of 'source functions'. - functions.sh: Consistent quoting in foreach_plugin function. - functions.sh: Change the contract of start_nbdkit so it

...kit on exit, most scripts no longer need to deal with the pid or kill the pid in the cleanup function. - As a result, cleanup functions are radically simpler, and often disappear completely. - Also removed the comment "# The cleanup() function is called implicitly on exit" passim partly because the cleanup functions have mostly been removed and partly because it should be clear from looking at functions.sh. There is one additional change: In the test-memory*.sh tests, nbdkit used to run in the foreground, but that seems to be a consequence of some left over debugging...