search for: progresstim

Displaying 7 results from an estimated 7 matches for "progresstim".

Did you mean: progresstime
2002 Jan 30
1
Quick sftp status indicator.
...2002/01/24 21:09:25 1.11 +++ misc.h 2002/01/29 23:16:28 @@ -30,4 +30,9 @@ int num; int nalloc; }; + void addargs(arglist *, char *, ...) __attribute__((format(printf, 2, 3))); +void progressmeter(int flag, off_t statbytes, off_t totalbytes, char *curfile); + +#define PROGRESSTIME 1 /* alarm() interval for updating progress meter */ + Index: scp.c =================================================================== RCS file: /cvs/src/usr.bin/ssh/scp.c,v retrieving revision 1.86 diff -u -r1.86 scp.c --- scp.c 2001/12/05 03:56:39 1.86 +++ scp.c 2002/01/29 23:16:29 @@ -83,24...
2002 Feb 06
2
SFTP Status Bar..
...Jul 4 12:25:55 2001 +++ openssh/misc.h Wed Feb 6 13:02:33 2002 @@ -29,7 +29,11 @@ int num; int nalloc; }; + void addargs(arglist *, char *, ...) __attribute__((format(printf, 2, 3))); +void progressmeter(off_t statbytes, off_t totalbytes, char *curfile); + +#define PROGRESSTIME 1 /* alarm() interval for updating progress meter */ /* wrapper for signal interface */ typedef void (*mysig_t)(int); diff -ur openssh-3.0.2p1/scp.c openssh/scp.c --- openssh-3.0.2p1/scp.c Sun Oct 21 19:53:59 2001 +++ openssh/scp.c Wed Feb 6 13:07:33 2002 @@ -89,32 +89,12 @@ char *__progn...
2002 Feb 02
0
Version two of progressbar for scp/sftp
...--- misc.h 2002/01/24 21:09:25 1.11 +++ misc.h 2002/02/02 21:47:40 @@ -30,4 +30,8 @@ int num; int nalloc; }; + void addargs(arglist *, char *, ...) __attribute__((format(printf, 2, 3))); +void progressmeter(off_t statbytes, off_t totalbytes, char *curfile); + +#define PROGRESSTIME 1 /* alarm() interval for updating progress meter */ Index: scp.c =================================================================== RCS file: /cvs/src/usr.bin/ssh/scp.c,v retrieving revision 1.86 diff -u -r1.86 scp.c --- scp.c 2001/12/05 03:56:39 1.86 +++ scp.c 2002/02/02 21:47:40 @@ -83,24 +...
2002 May 14
0
[Bug 241] New: When I kill scp, the underlying ssh child process remains alive
...,196 **** --- 196,203 ---- *fdout = pin[1]; close(pout[1]); *fdin = pout[0]; + /* esb */ + (void) signal(SIGTERM, killchild); return 0; } *************** *** 1086,1091 **** --- 1093,1105 ---- signal(SIGALRM, updateprogressmeter); alarm(PROGRESSTIME); errno = save_errno; + } + + static void + killchild(int signo) + { + kill (childpid, signo); + _exit(1); } static int ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
2023 May 05
0
Calls running forever / CDRs inaccurate
...13h4m11s Bridge ID: (Not bridged) -- PBX -- Context: customer-voipin Extension: 49xxxxxxxxx Priority: 26 Call Group: 0 Pickup Group: 0 Application: Dial Data: SIP/+49xxxxxxxx at provider Call Identifer: [C-000085c3] Variables: PROGRESSTIME_MS= PROGRESSTIME= RINGTIME_MS= RINGTIME= DIALEDTIME_MS= DIALEDTIME= ANSWEREDTIME_MS= ANSWEREDTIME= DIALEDPEERNAME= DIALEDPEERNUMBER= DIALSTATUS= SIPADDHEADER02=X-Something: something AUTO_MONITOR=wav,/var/spool/asterisk/monitor/20230505110016-customer-DE-EXTEN-49xxxxxxx-CLINUM-49xxxxxxxxx-CLINAME-...
2002 Jul 13
0
[PATCH]: scp program improved
...t; width); i++) + temp[i] = '='; + + if (i < width) + temp[i] = '>'; + + for (i++; i < width; i++) + temp[i] = '-'; + + snprintf(buf, MAX_GAUGELEN, "[%s]", temp); +} - if (flag == -1) { - mysignal(SIGALRM, updateprogressmeter); - alarm(PROGRESSTIME); - } else if (flag == 1) { - alarm(0); - atomicio(write, fileno(stdout), "\n", 1); - statbytes = 0; - } +void progressmeter(int flag) +{ + static const char indicator[] = "|/-\\"; + static struct timeval lastupdate; + static off_t lastsize; + struct timeval now, td,...
2009 Jan 06
5
Simple CDRs
Greyman-- I'm taking this discussion to the list. Folks, what we are talking about here, is me trying to get a grasp around Greyman's (Aaron's) request for a bare-bones CDR generation that describes just total connect time for channels, stripping out all the details. Who cares about xfer, park, hold, etc.? So in the following is our discussion about what *should* be there, and in