Troubleshooting VNC
From FarmShare
(Difference between revisions)
(Created page with "== Resetting the shell configuration == Some kinds of changes to ~/.cshrc and ~/.login (or other shell configuration files) may break VNC; in particular, setting up the environme...") |
|||
| (9 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | == Resetting the shell configuration == | + | == Quota conditions == |
| - | Some kinds of changes to ~/.cshrc and ~/.login (or other shell configuration files) may break VNC; in particular, setting up the environment for certain applications (e.g., [[Cadence|Cadence]]) according to instructions is known to cause problems. | + | |
| - | + | '''farmvnc''' may not start if you are over your [[AFS|AFS]] quota. | |
| - | == Resetting VNC state and configuration == | + | |
| - | A common troubleshooting method is to reset the VNC configuration by deleting the ~/.vnc application directory. | + | == Authentication == |
| - | rm -rf ~/.vnc | + | |
| + | Likewise, farmvnc may not start if you do not have a valid Kerberos ticket and [[AFS]] tokens. Try re-authenticating before running the command. | ||
| + | <pre>kinit && aklog</pre> | ||
| + | |||
| + | == Resetting the shell configuration == | ||
| + | |||
| + | Some kinds of changes to ~/.cshrc and ~/.login (or other shell configuration files) may break VNC; in particular, setting up the environment for certain applications (e.g., [[Cadence|Cadence]]) according to instructions is known to cause problems. The default configuration for various shells is documented in [[Dotfiles]]. | ||
| + | |||
| + | == Resetting VNC state and configuration == | ||
| + | |||
| + | A common troubleshooting method is to reset the VNC configuration by deleting the ~/.vnc application directory. | ||
| + | <pre>rm -rf ~/.vnc | ||
mkdir ~/.vnc | mkdir ~/.vnc | ||
| - | vncpasswd | + | vncpasswd</pre> |
| + | |||
---- | ---- | ||
| + | |||
Search the farmshare-discuss archives for posts about [https://mailman.stanford.edu/mailman/swish?query=VNC&submit=Search+farmshare-discuss%21&metaname=swishdefault&sort=unixdate&listname=farmshare-discuss VNC]. | Search the farmshare-discuss archives for posts about [https://mailman.stanford.edu/mailman/swish?query=VNC&submit=Search+farmshare-discuss%21&metaname=swishdefault&sort=unixdate&listname=farmshare-discuss VNC]. | ||
Latest revision as of 15:39, 17 September 2014
Contents |
Quota conditions
farmvnc may not start if you are over your AFS quota.
Authentication
Likewise, farmvnc may not start if you do not have a valid Kerberos ticket and AFS tokens. Try re-authenticating before running the command.
kinit && aklog
Resetting the shell configuration
Some kinds of changes to ~/.cshrc and ~/.login (or other shell configuration files) may break VNC; in particular, setting up the environment for certain applications (e.g., Cadence) according to instructions is known to cause problems. The default configuration for various shells is documented in Dotfiles.
Resetting VNC state and configuration
A common troubleshooting method is to reset the VNC configuration by deleting the ~/.vnc application directory.
rm -rf ~/.vnc mkdir ~/.vnc vncpasswd
Search the farmshare-discuss archives for posts about VNC.
