I'm curious why some of the si_ commands are now restarting rsyncd every time they complete, si_cpimage and si_mvimage for example. I have some automatted processes that are being really hosed by the rsync daemon getting bounced in the middle of reads.
A few questions: Isn't there a little concern that restarting rsyncd this much could potentially hose clients pulling an image? Peeking at the source of rsync on my systems it reloads its configuration file each time a client connects, so I don't understand the commit comment that went with this change: "- fix: restart systemimager-server-rsyncd after a moving, removing or copying an image to refresh the view of si_lsimage". ( I tested this, and I immediately see any additions to rsyncd.conf in my rsyncd output... ) Is there an older version where this isn't true maybe? Thanks! Matt ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
