Opened 9 years ago
Closed 9 years ago
#30437 closed enhancement (fixed)
More accurate post-activate logic for fuse4x
Reported by: | anatol (Anatol Pomozov) | Owned by: | drkp (Dan Ports) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.0 |
Keywords: | Cc: | ||
Port: | fuse4x-kext |
Description
post-activate logic for fuse4x-kext should be following:
- (Optional step) Check if kext is running: "kextstat -lb org.fuse4x.kext.fuse4x". if it is not running - we are done.
- unload the kext using "sudo kextunload -b org.fuse4x.kext.fuse4x". In case if nobody uses kext this operation should be successful.
- check if the kext is still running. if it is not running - we are done.
- if previous step shown that the kext is still running - it means that somebody still uses it. We need to ask user either to stop all filesystems and unload kext manually or restart the computer. The list of mounted fuse4x filesystems can be found via "mount -t fuse4x"
Change History (3)
comment:1 Changed 9 years ago by drkp (Dan Ports)
Cc: | dports@… removed |
---|---|
Owner: | changed from macports-tickets@… to dports@… |
Status: | new → assigned |
comment:2 Changed 9 years ago by jmroot (Joshua Root)
Type: | request → enhancement |
---|
comment:3 Changed 9 years ago by drkp (Dan Ports)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Thanks. I noted that in our earlier discussions, but triaged it as something relatively low-priority to fix after adding the fuse4x port.