keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.89k stars 1.23k forks source link

How to restart? #3393

Open jsejcksn opened 8 years ago

jsejcksn commented 8 years ago

Do I have to manually restart each launchd process at present? How does launching and quitting the GUI affect this?

keybase launchd restart keybase.service
keybase launchd restart keybase.kbfs
keybase launchd restart keybase.updater
AlexisWilke commented 5 years ago

Under Linux I had to do this:

run_keybase

Then I got the file system back (along with the window and a squirrel in my console.) I'm not too sure about the details, but that run_keybase command is a script so you can probably check inside there to see what they do.

daveyarwood commented 5 years ago

I saw in the run_keybase help text that there is a -k (shut down all Keybase services) flag.

So, you can restart keybase by running:

run_keybase -k && run_keybase
ghost commented 5 years ago

How to do it on Windows machine?

totedati commented 4 years ago

Or on systemd enabled distros, like is my kubuntu bionic beaver 18.04, you should simply restart kbfs filesystem: systemctl --user restart kbfs.service

Can be done from user console terminal no need for root acces because kbfs is a fuse fs anyway

Look like when you do a logout/login round kbfs filesystem is left in an inconsistent state and any cd /keybase console command spite this strange error

/keybase: Transport endpoint is not connected

In file $(which run_keybase) you can see all this commands but for

Transport endpoint is not connected

error a full keybase restart i think is too much, on my case gui applet is here and i can open main keybase gui app windows, only kbfs is fluffy