similar to: DO NOT REPLY [Bug 4139] New: Generator process (running as daemon) hangs after kill SIGINT.

Displaying 20 results from an estimated 400 matches similar to: "DO NOT REPLY [Bug 4139] New: Generator process (running as daemon) hangs after kill SIGINT."

2007 Nov 12
3
DO NOT REPLY [Bug 5075] New: Syncing with --iconv may yield protocol error
https://bugzilla.samba.org/show_bug.cgi?id=5075 Summary: Syncing with --iconv may yield protocol error Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: lennart.samba@lovstrand.com
2002 Sep 25
0
stack overflow
Hi everybody, I use rsync v2.5.5 almost without problems, but it dumps core from time to time. Core was generated by `rsync'. Program terminated with signal 11, Segmentation fault. There is excerpt from gdb's bt: #0 0x2810106f in __sfvwrite () from /usr/lib/libc.so.4 #1 0x280fdfe1 in fprintf () from /usr/lib/libc.so.4 #2 0x281002b6 in vfprintf () from /usr/lib/libc.so.4 #3
2001 Dec 18
3
rsync hang, more details [LONG]
rsync 2.5.0 still has a bug where it hangs under some circumstances. The hang is beyond my abilities to track down. I'll keep trying, though, but here are details in case they're of use to anyone else: - Code configured & built on Solaris 2.5.1. - Same binary run on Solaris 2.5.1 (client) and 2.8 (server). - Using rsh transport, but also fails with ssh - Does not fail with
2011 Apr 09
1
[Bug 8073] New: Regress: 3.0.8 cannot compile on freebsd
https://bugzilla.samba.org/show_bug.cgi?id=8073 Summary: Regress: 3.0.8 cannot compile on freebsd Product: rsync Version: 3.0.8 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: blocker Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: grarpamp at gmail.com
2002 Oct 13
1
rsync 2.5.5 core dump
-----BEGIN PGP SIGNED MESSAGE----- I added the following code to log_exit(): void log_exit(int code, const char *file, int line) { static int error_count=0; if(error_count++ > 10) { abort(); } To force it to bail earlier instead of overflowing the stack. As you can see at frame #50, it is trying to log that the connection went away unexpectantly.
2002 Jan 13
0
rsynd-2.5.1 / io.c patches
Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the IO.C module. The (char) type was being used where (void) was more appropriate based on the actual use of the code. The (char) type was also being used where the usage was actually an (unsigned char). const qualifiers were added to improve compile efficiency. EAGLE> type
2011 May 15
0
rsync client and server processes, all hanging in read_timeout()
I'm backing my Ubuntu server up to an HFS+ case-sensitive volume on our iMac using the below rsync command and it hangs at the end. Compiling rsync 3.0.8 by hand with CFLAGS=-g on both systems shows that all rsync processes are in read_timeout(). $ rsync \ --delete-delay \ -P \ -v \ -A \ -X \ --fake-super \ -aH \ --numeric-ids \ --exclude '/dev' \
2008 Feb 27
2
DO NOT REPLY [Bug 5287] New: FreeBSD pre10 compilation warnings report
https://bugzilla.samba.org/show_bug.cgi?id=5287 Summary: FreeBSD pre10 compilation warnings report Product: rsync Version: 3.0.0 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: 14709c93@mailinator.com
2002 Jul 02
1
Rsync: Segmentation fault
Rsync 2.5.5; transfer via ssh; sparc-sun-solaris2.5 (Ultra 1); gcc 2.8.1. Every time rsync on this box causes boundary violation. I attached two strange examples. I have a few rsync's corefiles (100MB and above) and I can examine them. I will be grateful for any help. -Mirek <-------------------------------------------------------------------------> received 966761 names done
2007 Apr 13
1
spec''ing out a trap/SIGINT
How would you spec out a call to Signal.trap (a ^C or a unix SIGINT)? Scott
2006 May 12
0
win32-process 0.4.0 - SIGINT/SIGBRK not working
Hello, I''ve been trying to use the PureRuby win32 process gem. This is my child.rb file: # child.rb puts "child process #{Process.pid} started at #{Dir.getwd}" trap("INT") { puts "SIGINT signal received." exit(1) } trap("TERM") { puts "TERM signal received." exit(1) } trap("KILL") { puts "KILL signal
2004 Nov 20
0
SIGINT in win32-process
Hi all, I banged my head all day trying to make SIGINT work like you would expect on Win32, to no avail. The goal is to allow the user to send a SIGINT (i.e. CTRL_C_EVENT) to a remote process. I tried a CreateRemoteThread() + GenerateConsoleCtrlEvent() approach with no luck. I also found this bit of code:
2007 Jun 14
0
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
Hi, I am encountering a error saying-rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229). This error was encountered after 2.5hrs of rsync. What does this exactly mean? I am pretty new the whole concept so not able to figure it out. Regards, Madhavan Chari -------------- next part -------------- HTML attachment scrubbed and removed
2006 Oct 05
0
Rsync error:received SIGUSR1 or SIGINT (code 20) at rsync.c(231)
I'm trying to transfer thousands of file from a remote machine to my server.Every-time I do this, I'm getting error saying "received SIGUSR1 or SIGINT (code 20) at rsync.c(231)".Pl. suggest me what could be wrong and how can I rectify this. The command i'm using is rsync -avz --copy-links --delete childes.psy.cmu.edu::CHILDES /var/www/localhost/htdocs/childes
2005 Oct 17
0
[Bug 2760] some time rsync is exiting with received SIGUSR1 or SIGINT (code 20) at rsync.c(229).
https://bugzilla.samba.org/show_bug.cgi?id=2760 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From wayned@samba.org 2005-10-17 11:01
2002 Feb 12
1
rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
Trying to rsync between win2k machines. rsync version is 2.5.3pre (downloaded today) This is the message after 368100 files have been checked: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) My cmdline is : c:\sbin\rsync\rsync -az /cygdrive/d/Home xxx@xxx.skelleftea.se::dropZone/GY/ba-disk01 --stats -v -P --timeout=84600 I have tried with both with and without -z (-az or -a)
2004 Jun 30
1
"break"/SIGINT handling
Hi, Could anyone tell me why break requests are only handled in sshd if the channel type is in a 'LARVAL' state? I'm converting an application that currently uses telnet as an underlying communication protocol and it relies on a SIGINT when an IAC/IP is received by the telnet daemon. It seems an SSH break could/should perform a similar function (tcsendbreak() in session_break_req()
2015 Aug 11
0
[Bug 1859] sshd does not forward break request to process as SIGINT
https://bugzilla.mindrot.org/show_bug.cgi?id=1859 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Damien Miller <djm at mindrot.org> --- Set all RESOLVED bugs to CLOSED with release
2009 Nov 11
1
v2.0.tip master: service(auth): kill(pid, SIGINT) failed: Operation not permitted
Hi Timo, I've configured the user nobody for the the service auth. doveconf -n # 2.0.alpha3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.30-1-amd64 x86_64 Debian squeeze/sid ? service auth { user = nobody } ? The other processes are executed by root (or logged in user): root 8758 0.0 0.0 2604 1052 ? Ss 07:21 0:00 /usr/local/sbin/dovecot root 8759 0.0
2014 Jan 16
1
SIGINT is a bad choice for changing log levels
Guus, I would like to ask you to reconsider using SIGINT for logging change. It?s a pain to kill tincd when started from the command line. Ctrl-C does not work as expected. Great for debugging perhaps, but in normal use cases, when trying to make a connection work and test changes it?s a pain. On BSD there is SIGINFO (29), which can be sent by pressing Ctrl-T, but I am not sure whether that