New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qvm-copy-to-vm2 doesn't inform the user when the copy operation is complete #161

Closed
marmarek opened this Issue Mar 8, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 29 Mar 2011 13:03 UTC
In other words, the user has no idea when the transfer completed...

Migrated-From: https://wiki.qubes-os.org/ticket/161

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by rafal on 30 Mar 2011 14:15 UTC
qvm-copy-to-vm2 does not actually perform copying - it just signals qrexec-agent to do it. Thus, it has no idea when the transfer is done.

We would need another script, e.g. qvm-copy-to-vm2-with-status, that will poll qfile-agent for status/progress of the transfer. It can even print a text progress indicator, say print "XXX/YYY MB done"- the same way that GUI (qvm-copy-to-vm2.kde) does.

What should be the name of the script ? Should it provide text progress ?

Member

marmarek commented Mar 8, 2015

Comment by rafal on 30 Mar 2011 14:15 UTC
qvm-copy-to-vm2 does not actually perform copying - it just signals qrexec-agent to do it. Thus, it has no idea when the transfer is done.

We would need another script, e.g. qvm-copy-to-vm2-with-status, that will poll qfile-agent for status/progress of the transfer. It can even print a text progress indicator, say print "XXX/YYY MB done"- the same way that GUI (qvm-copy-to-vm2.kde) does.

What should be the name of the script ? Should it provide text progress ?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 30 Mar 2011 14:17 UTC
The name should be qvm-copy-to-vm (without also the confusing 2). Just that if we wanted to use it from some other tool (GUI action script), then we should use the same script with just some special switches.

Member

marmarek commented Mar 8, 2015

Comment by joanna on 30 Mar 2011 14:17 UTC
The name should be qvm-copy-to-vm (without also the confusing 2). Just that if we wanted to use it from some other tool (GUI action script), then we should use the same script with just some special switches.

@marmarek

This comment has been minimized.

Show comment
Hide comment
Member

marmarek commented Mar 8, 2015

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment