You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use ZFS on our LTSP server, which is configured so that each users home dir has its own dataset. Users are able to access files in their home dir snapshots via the .zfs special directory but unfortunately httm doesn't work when run on the LTSP clients directly, they get the error:
Error: httm could not find any valid datasets on the system
The workaround is for users to ssh into the LTSP server, then httm works as expected but it'd be nice if users could use httm on LTSP clients without having to ssh into the server first.
The text was updated successfully, but these errors were encountered:
Users are able to access files in their home dir snapshots via the .zfs special directory but unfortunately httm doesn't work when run on the LTSP clients directly, they get the error:
In all likelihood (if the snapshots are visible to the users) this is because the mounts aren't visible to the users, or aren't visible as ZFS mounts. If you expose /proc/mounts or have the users mount their shares locally via an SMB, it should work. See the README concerning the use of network mounts (and specifically aliases).
Any extensive work re: LTSP support from me is unlikely, because I don't use it! But httm is ready made for the clever sysadmin to make this work. And I'd be pleased to add support which is harmonious with the rest of the system. For instance, if mounts simply appear differently to an LTSP users and can readily be interpreted as ZFS mounts, like say a SMB share, with a .zfs/snapshots directory, I'd be pleased to add support.
We use ZFS on our LTSP server, which is configured so that each users home dir has its own dataset. Users are able to access files in their home dir snapshots via the .zfs special directory but unfortunately
httm
doesn't work when run on the LTSP clients directly, they get the error:The workaround is for users to ssh into the LTSP server, then httm works as expected but it'd be nice if users could use httm on LTSP clients without having to ssh into the server first.
The text was updated successfully, but these errors were encountered: