The messages on guest's screen:

# ./guestfsd -vr
verbose daemon enabled
linux commmand line: BOOT_IMAGE=/boot/vmlinuz-3.5.3-1.fc17.i686.PAE root=UUID=88c7691f-a407-45ad-a2b2-c00f0d7c24cc ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet

guestfsd: main_loop: new request, len 0x28
fsync /dev/vda
fsync /dev/vdb
guestfsd: main_loop: proc 282 (internal_autosync) took 0.23 seconds
read: unexpected end of file on fd 3

You can see the last line.

thanks.

On Thu, Sep 13, 2012 at 6:01 PM, Richard Huang <huangyunsong@gmail.com> wrote:
Since the guestfsd is already dead, that means there is no guestfsd process in the guest, then guestfish cannot execute "run" with --live option any more.

In Fedora 17, there is guestfsd.service which uses systemd restart function to bring the guestfsd up I guess..


On Thu, Sep 13, 2012 at 5:57 PM, Wanlong Gao <gaowanlong@cn.fujitsu.com> wrote:
On 09/13/2012 05:52 PM, Richard Huang wrote:
> I've compiled guestfsd and run it on CentOS 6.3. It worked well, but when I quit guestfish, the guestfsd process in guest is always dead itself automatically. Is this a bug? or did I miss something?
>

Yeah, the guestfsd should be dead when you finish your operations to the guest,
and will be started when you use guestfish next time. It's the design of guestfs,
not a bug.

Thanks,
Wanlong Gao

> thanks.
>
>
> _______________________________________________
> Libguestfs mailing list
> Libguestfs@redhat.com
> https://www.redhat.com/mailman/listinfo/libguestfs
>