> To shut down the web server, run lsof -i :19421 to get the PID of the process, then do kill -9 [process number]. Then you can delete the ~/.zoomus directory to remove the web server application files.
> To prevent this server from being restored after updates you can execute the following in your terminal:
note the last part where the directory is removed (~/.zoomus) and touch creates a file ~/.zoomus. I am assuming a re-install will fail because it cannot create a directory again when there is already an existing file.
My guess is that if sometime in the future you want to use zoom again, the install will fail until you remove the file ~/.zoom
Doing it that way results in a nuisance prompt from Zoom every time you launch it complaining that it can't launch the opener.
Here's a modified version that deletes the app, removes the LoginItem if it exists, and makes the ~/.zoomus directory unwritable, which achieves the same thing but avoids the nag:
From the article:
> To shut down the web server, run lsof -i :19421 to get the PID of the process, then do kill -9 [process number]. Then you can delete the ~/.zoomus directory to remove the web server application files.
> To prevent this server from being restored after updates you can execute the following in your terminal:
rm -rf ~/.zoomus
touch ~/.zoomus
note the last part where the directory is removed (~/.zoomus) and touch creates a file ~/.zoomus. I am assuming a re-install will fail because it cannot create a directory again when there is already an existing file.
My guess is that if sometime in the future you want to use zoom again, the install will fail until you remove the file ~/.zoom
I did this: 1. killed by process name, and zoom app will 2. fail to start its opener and 3. fail to reinstall it:
Doing it that way results in a nuisance prompt from Zoom every time you launch it complaining that it can't launch the opener.
Here's a modified version that deletes the app, removes the LoginItem if it exists, and makes the ~/.zoomus directory unwritable, which achieves the same thing but avoids the nag:
3 replies →
Not sure why he didn't just give us
For the non bash users among us?
5 replies →