search for: setlinebuf

On Fri, 26 Oct 2001, Larry Rosenman wrote: :I tried to compile OpenSSH 2.9.9p2 on my Caldera OpenUNIX8 system and :it couldn't find setlinebuf. setlinebuf is a BSD compatibility :function. It was called from sftp-int.c. Looking at the code, there :is a #ifdef for HAVE_SETVBUF, but apparently configure isn't set to :look for setvbuf (which we DO have). : :I added a #define HAVE_SETVBUF 1 to config.h, and this problem goes :away. co...

dash didn't compile in DEBUG mode against klibc for all long time. Now it fails at link stage for not having setlinebuf(3). Fixes: usr/dash/show.o: In function `opentrace': show.c:(.text+0x86): undefined reference to `setlinebuf' Signed-off-by: maximilian attems <max at stro.at> --- the last open error, looks more like a klibc bug to me, will fix it there: show.c:(.text+0x36)...

dash didn't compile in DEBUG mode against klibc for all long time. Now it only fails at link stage for not having setlinebuf(3) and freopen(3). Fixes: usr/dash/show.o: In function `opentrace': show.c:(.text+0x36): undefined reference to `freopen' show.c:(.text+0x86): undefined reference to `setlinebuf' Skip setlinebuf and use fclose/fopen inside SMALL. Signed-off-by: maximilian attems <max at stro.at&g...

dash didn't compile in DEBUG mode against klibc for all long time. Now it only fails at link stage for not having setlinebuf(3) and freopen(3). Fixes: usr/dash/show.o: In function `opentrace': show.c:(.text+0x36): undefined reference to `freopen' show.c:(.text+0x86): undefined reference to `setlinebuf' Skip setlinebuf and use fclose/fopen inside __KLIBC__ Compile tested with debug in klibc and against glib...

...t was seem that the compiler include all stdio.h functions and compile all them. I would like somebody of list to clear my doubt. Regards, Cleviton. Here below small script used I grasp on site: http://home.cogeco.ca/~camstuff/agi.html /* C works just fine with Asterisk but you should use 'setlinebuf' on stdout and stderr. This causes buffering one line at a time (rather than using a larger buffer). If you *don't* do this on stdout then your script will hang up while Asterisk waits for a command but the (long) buffer isn't full yet. A minimal AGI script in C looks like this: */ //...

...orDate: Fri, 15 Jul 2011 11:18:13 +0800 Committer: maximilian attems <max at stro.at> CommitDate: Mon, 2 Jul 2012 10:45:52 +0200 [klibc] [SHELL] Fix klibc DEBUG compilation dash didn't compile in DEBUG mode against klibc for all long time. Now it only fails at link stage for not having setlinebuf(3) and freopen(3). Fixes: usr/dash/show.o: In function `opentrace': show.c:(.text+0x36): undefined reference to `freopen' show.c:(.text+0x86): undefined reference to `setlinebuf' Skip setlinebuf and use fclose/fopen inside __KLIBC__ Compile tested with debug in klibc and against glib...

...e "Hello, world!" of AGI in C. The following doesn't work: The file never gets written: =========== //check_cid.c #include <stdio.h> #include <stdlib.h> #include <syslog.h> #include <string.h> int main(int argc, char *argv[]) { char line[80]; int i; setlinebuf(stdout); setlinebuf(stderr); FILE *file; file = fopen("file.txt","a+"); while (1) { fgets(line,80,stdin); fprintf(file,"%s",line); if (strlen(line) <= 1) break; } fclose(file); return(EXIT_SUCCESS); } =========== This is how...

...ix dash allmost compiles in DEBUG mode, the last two failures happen in show.c, which assumes some buffering functions that klibc doesn't provide: usr/dash/show.o: In function `opentrace': show.c:(.text+0x36): undefined reference to `freopen' show.c:(.text+0x86): undefined reference to `setlinebuf' afais this code dates from the initial git import. any preferences on how to fix those Herbert? -- maks

Hi, I've looked at the Wiki for this, have seen the Swift.agi details, but has anyone got a current script for Cepstral and an example of integraton in * please? I'm a * and linux newbie, so please be gentle ;-) Thanks John

Hi I am currently developing a IVR application using PHP/AGI. I am using the PHPAGI class at http://phpagi.sourceforge.net/ to handle the commuication with my *. The application basically asks a caller to enter in some information which is then processed and a answer is read back out to them. I want the application to loop back to the beginning after giving the answer so they can try another

Hi Most of our customers have generic names like "Hospital", so I need to rewrite their caller ID name by looking up the number in a database on the Asterisk server, and rewriting the name such as "Reading Hospital" so that we know who's calling. Any idea if this can be done with Asterisk, and how to do it? Thank you.

...s. Well, its simple, either asterisk is not sending correctly the command responses to the standard output, or for some unknown reason to me the scripts/programs are not able to read it from standard input. I have the next C test program for AGI: #include <stdio.h> main() { char line[80]; setlinebuf(stdout); setlinebuf(stderr); while (1) { fgets(line,80,stdin); if ( strlen(line) <= 1 ) { break; } } printf("SAY NUMBER 55 \"\"\n"); fgets(line,80,stdin); printf("SAY NUMBER 66 \"\"\n"); fgets(line,80,stdin); } I currently have...

...some problems about this old and specific system. 1. It does not have setvbuf(). 2. It does not have 'struct utimbuf'. 3. It has 'O_NONBLOCK' in <stream/xti.h>. 4. It does not have 'WNOHANG'. I don't know why. The setvbuf() can be replaced with setbuffer() and setlinebuf(), for example, I wrote --->8------>8------>8------>8------>8------>8------>8------>8--- Index: lib/getsmbpass.c =================================================================== RCS file: /home/nakaji/ncvs/samba-news4/source/lib/getsmbpass.c,v retrieving revision 1.1.1.1...

...handled key-types can be detected by checking if the line begins with whitespace. The current behaviour working as well as it does is based on only one set of keys being loaded and the most portable keys being loaded first. The current behaviour can be made agnostic of tty/non-tty by inserting a `setlinebuf(stdout);` call into `list_identities()`. A more reliable approach might be to give `key_fingerprint()` a flag to avoid calling fatal and to return an error some other way? -- You are receiving this mail because: You are watching the assignee of the bug.

...33fbee8, 0x7ffff4a0f998, 0x7ffff4a0f9d0, 32) = 0x55591472dbf0 20582 smb_init_locale(0x7ffff4a0f860, 0x55591347b1a0, 0x55591472db80, 0) = 0x555914732c30 20582 zero_sockaddr(0x7ffff4a0f660, 0x7f3e4c71b46c, 1, 0) = 2 20582 setlinebuf(0x7f3e4dc36500) = <void> 20582 setup_logging(0x555913401189, 3, 0, 0) = 1 20582 lp_set_cmdline(0x5559133fc8b3, 0x5559134010c4, 0x7f3e4e0da668, 0x746e65696c636370) = 1 20582...

...ing for unistd.h... (cached) yes checking whether time.h and sys/time.h may both be included... yes checking for pid_t... yes checking for size_t... yes checking return type of signal handlers... void checking for strftime... yes checking for vsnprintf... yes checking for setsid... yes checking for setlinebuf... yes checking whether build environment is sane... yes checking for gawk... gawk checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking whether to enable maintainer-specific portions of Makefiles... no checking for a sed that does not truncate output.....

...ing for unistd.h... (cached) yes checking whether time.h and sys/time.h may both be included... yes checking for pid_t... yes checking for size_t... yes checking return type of signal handlers... void checking for strftime... yes checking for vsnprintf... yes checking for setsid... yes checking for setlinebuf... yes checking whether build environment is sane... yes checking for gawk... gawk checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking whether to enable maintainer-specific portions of Makefiles... no checking for a sed that does not truncate output.....

...r lseek64... no > checking for ftruncate64... no > checking for readdir64... no > checking for fseek64... no > checking for fseeko64... no > checking for ftell64... no > checking for ftello64... no > checking for setluid... no > checking for getpwanam... no > checking for setlinebuf... no > checking for srandom... no > checking for random... no > checking for srand... no > checking for rand... no > checking for setenv... no > checking for usleep... no > checking for strcasecmp... no > checking for fcvt... no > checking for fcvtl... no > checking f...

...t... yes checking for dup2... yes checking for lseek64... no checking for ftruncate64... no checking for readdir64... no checking for fseek64... no checking for fseeko64... no checking for ftell64... no checking for ftello64... no checking for setluid... no checking for getpwanam... no checking for setlinebuf... yes checking for srandom... yes checking for random... yes checking for srand... yes checking for rand... yes checking for setenv... yes checking for usleep... yes checking for strcasecmp... yes checking for fcvt... yes checking for fcvtl... no checking for symlink... yes checking for readlink.....

...s checking for size_t... (cached) yes checking return type of signal handlers... (cached) void checking for strftime... (cached) yes checking for vsnprintf... (cached) yes checking for setpgid... (cached) yes checking for inet_addr... (cached) yes checking for inet_aton... (cached) yes checking for setlinebuf... (cached) yes checking for shout/shout.h... (cached) no Installed libshout not found, using builtin checking for lame/lame.h... (cached) no checking for lame.h... (cached) no Could not find a valid LAME library, reencoding disabled checking for perl_construct... (cached) yes checking for Python.h...