![]() In the terminal, I received the same pop-up window as before with this message: I was able to find teamviewerd in the system services and check the box, then clicked 'ok'. To start the teamviewer daemon use System services under system orĪs root make /etc/rc.d/rc.teamviewerd executable and then as root execute /etc/rc.d/rc.teamviewerd start I can't find the actual command after the process is finished. ![]() I wouldn't know how to retrieve it anyway. 'sudo spi -i teamviewer' created so much output that I don't think I should post it here. An error (15) occurred when creating archive /tmp/tvlog_darkstar_.zip Zip error: Could not create output file (was replacing the original zip file)ĭone. ![]() ![]() Zip warning: new zip file left as: /tmp/zi9ZpYHY Updating: sysinfo/dbus-send (deflated 76%) Updating: sysinfo/Xorg.0.log.old (deflated 83%) Updating: sysinfo/ifconfig (deflated 56%) Updating: sysinfo/Xorg.0.log (deflated 83%) Updating: logfiles/TeamViewer10_Logfile.log (deflated 86%) Updating: config/teamviewerd.pid (stored 0%) Rm: cannot remove ‘/tmp/tvlog_darkstar_.zip’: Operation not permitted Otherwise you'll just have to kludge together a script executed on the Guest that will restart the VM using vmrun from the Host.Creating a zip archive from all files in logfiles and configĭmesg: klogctl failed: Operation not permitted There are many way to spawn and monitor a process so it can automatically be re-spawned, it just depends on what the Host OS is and how good your programming skills are. The guest OS could be configured to only shutdown not reboot so as to force the disk to be flushed. Of course the User will loose connectivity to the Guest during this time however that is unavoidable and they'll just have to reestablish a connection in a couple of minutes.Īnother option would be to start the VM in such a manner that the vmware-vmx process is being monitored so that when it terminates it is restarted automatically thus the user would only need to shutdown the VM and wait for it to be ready to be logged into again. However since the user is connecting to the Guest OS, not the Host OS, you'll have to setup and manage a scripted solution that is executed on the Guest to run on the Host that will restart the VM after it has shutdown so the ""Independent - Nonpresistent" mode" disk can be flushed. Wil mentioned using vmrun and of course this is done on the Host not from within the Guest which is what you're looking for. Ovrum wrote: So my goal is that people can connect to the demo images with TeamViewer, do their thing and be able to revert to a snapshot from inside the image. I was hoping the way i did it would work with a easy reboot but after testing its only working when you Shut Down, and thats not very helpful when running demo images.ĭo anyone have any ideas on how to set this up? So my goal is that people can connect to the demo images with TeamViewer, do their thing and be able to revert to a snapshot from inside the image. Set the command snapshot.action = "autoRevert" Turned on "Independent - Nonpresistent" mode on the harddisks so that changes are discarded when you power off or restore a snapshot.Ģ. The problem im facing is that people are not cleaning up after they are done testing so i created a simple bat file to execute a reboot of the image after use but i cant seem to get Vmware to automaticly revert to a spesific snapshot or just revert to anything.ġ. So i got the task of setting up a test enviroment in vmware and the images are complete but the thing is that we got around 6-7 demo images where a lot of users can connect to with TeamViewer.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |