Displaying 3 results from an estimated 3 matches for "output_lock".
Did you mean:
output_local
2006 Jan 27
0
patch for bugs in vorbis-tools-1.1.1
..._c = now;
break;
diff -u -r X/VORBIS-TOOLS-1.1.1/OGG123/STATUS.C VORBIS-TOOLS-1.1.1/OGG123/STATUS.C
--- X/VORBIS-TOOLS-1.1.1/OGG123/STATUS.C 2005-06-03 11:15:09.000000000 +0100
+++ VORBIS-TOOLS-1.1.1/OGG123/STATUS.C 2006-01-21 01:22:16.000000000 +0100
@@ -316,6 +316,7 @@
void status_reset_output_lock ()
{
+ pthread_mutex_trylock(&output_lock);
pthread_mutex_unlock(&output_lock);
}
2010 Mar 21
3
2.0.beta3 imapd running hot
Hi,
since a couple of weeks I occasionally have an imapd going crazy on me,
using up 100% CPU. Current revision is 10962
29865 vmail 20 0 47820 3296 1708 R 99.7 0.9 131:07.85 imap
vmail 29865 86.1 0.8 47820 3296 ? R Mar20 131:20
dovecot/imap [berni 2001:a60:f001:1:219:66ff:fe8b:a6e IDLE
strace -p <pid> shows a repeating pattern of
epoll_wait(8, {{EPOLLOUT,
2002 Oct 05
2
ogg123 remote interface
...136,6 +136,36 @@
/* Statistics callbacks */
+/*
+// remote_write_action* functions :
+//
+// These functions are used from control_generic.c which is the ogg123
+// remote interface.
+//
+// Maybe add locking by calling a seperate (new) function in status.c
+// which holds its own output_lock for stdout.
+//
+*/
+void remote_write_action(buf_t *buf, void *arg)
+{
+ char *message = (char *)arg;
+
+ //status_message(0, "@%s", message);
+ fwrite(message, strlen(message), 1, stdout);
+ fwrite("\n", 1, 1, stdout);
+
+ free(message);
+ message = 0;
+}
+void remote_wr...