lipengyu / lsyncd

Automatically exported from code.google.com/p/lsyncd
GNU General Public License v2.0
0 stars 0 forks source link

v1.33,when setting <no-daemon/> will cause Segmentation fault #19

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. edit /etc/lsyncd.conf.xml
2. add <no-daemon/> fields
3. return to shell,run lsyncd

What is the expected output? What do you see instead?

SH_jjwxc135 log # lsyncd
Starting up
watching
Segmentation fault

What version of the product are you using? On what operating system?
lsyncd: v1.33 

Linux kernel : Linux SH_jjwxc135 2.6.26-gentoo-r3 #1 SMP Fri Dec 5 11:09:04 CST 
2008 x86_64 Quad-Core AMD Opteron(tm) Processor 2346 HE AuthenticAMD GNU/Linux

glibc version: 2.11

Please provide any additional information below.

1.when remove the <no-daemon/> setting ,lsyncd will ok
2.add <debug/> option,and remove <no-daemon/> in lsyncd.conf.xml,run lsyncd 
,will output this information :

.........

found new directory: <c in (null) -- P╜
found new directory: 嗷b in (null) -- P╜
found new directory: /var/www/gfs/abc.net/api.abc/var/Lair/Log/.. in (null) -- 
P╜
found new directory: <c in (null) -- P╜
found new directory: 嗷b in (null) -- P╜
found new directory: 
/var/www/gfs/abc.net/api.abc/www/scripts/dojo/io/xip_server.html in (null) -- 
P╜
found new directory: 
/var/www/gfs/abc.net/api.abc/www/scripts/dojo/cal/textDirectory.js in (null) -- 
P╜
found new directory: 
/var/www/gfs/abc.net/api.abc/www/scripts/dojo/dnd/HtmlDragAndDrop.js in (null) 
-- P╜
found new directory: 
/var/www/gfs/abc.net/api.abc/www/scripts/dojo/dot/ui-template/redball.png in 
(null) -- P╜
found new directory: p<d in (null) -- P╜

.........

strange symbol "P╜" ??

Original issue reported on code.google.com by Onio...@gmail.com on 9 Jun 2010 at 8:58

GoogleCodeExporter commented 9 years ago
the same issue is reported as Debian bug #585461 (see 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585461)

Original comment by jan.ditt...@gmail.com on 10 Jun 2010 at 7:04

GoogleCodeExporter commented 9 years ago
I suppose this has been fixed with 1.34

Original comment by axk...@gmail.com on 11 Jul 2010 at 7:14