Strange, I tested this with 2.6.9 (debian unstable) and 2.6.3 (RHEL4), and do not see this behavior...
# si_lsimage -------------------------------------------------------------------------------- Available image(s): -------------------------------------------------------------------------------- vmware vmware_copy_1 # si_mvimage vmware_copy_1 vmware_copy_2 # si_lsimage -------------------------------------------------------------------------------- Available image(s): -------------------------------------------------------------------------------- vmware vmware_copy_2 I'm curious if this is being caused by the filesystem on your server? Did you try just doing a "sync" after the mvimage command? On Friday 09 March 2007 02:29, Andrea Righi wrote: > Matt Jamison wrote: > > 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? > > Here is what happens with rsync 2.6.6 if the daemon is not restarted: > > # si_lsimage > --------------------------------------------------------------------------- >----- Available image(s): > --------------------------------------------------------------------------- >----- suse10 > > # si_mvimage suse10 suse10_tmp > # si_lsimage > --------------------------------------------------------------------------- >----- Available image(s): > --------------------------------------------------------------------------- >----- suse10 > suse10_tmp > > But this is not true, because there's only one image: suse10_tmp... > > Anyway, I agree, restarting rsync could generate some problems when you > copy, delete or move an image while the clients are imaging... > > Which version of rsync are you using? if with your version this problem > is solved I think we shouldn't care about the refresh and we could > remove the restart of the rsync daemon. I don't know if there's a better > solution for that... > > Regards, > -Andrea > > ------------------------------------------------------------------------- > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/sisuite-devel ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
