Am 22.01.19 um 20:23 schrieb Mike Gabriel: > Simply removing the USB flash drive is what is supposed to be done. If > the folder remains, then something goes wrong on the server-side (in > x2goumount-session), maybe in X2Go Client (dunno otoh).
Well, that's not what's happening. I was able to confirm the behavior on my test system. On the ThinClient, /media/Manufacturername/rawdevice # like sdb and /media/Manufacturername/partition # like sdb1 remain after unplugging the flash drive. I just checked, x2gousbmount contains a step to force-umount the media after removal, and to somehow let X2GoClient know about it by doing things in ~/export/, but it never contained a step to remove the directory *on the thinclient*. Also, it looks like the X2GoServer is simply monitoring directory existence on the thinclient - because as soon as you manually rmdir the empty directory on the thinclient, it also disappears from the server. I could simply add an rmdir step to the umount routine in x2gousbmount, but given what you wrote above, I'm wondering if it's supposed to happen somewhere else, and failing. Any insights? Should I proceed or go rmdir-grephunting across the X2Go source first? Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
signature.asc
Description: OpenPGP digital signature
_______________________________________________ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
