Difference between revisions of "Newsflashes"
Line 1: | Line 1: | ||
+ | <!-- | ||
===New Shortcuts=== | ===New Shortcuts=== | ||
Dr. G has created two pages describing some potentially handy UNIX shortcuts that you can add to your own accounts. For newer users, these are at [[BASH Shortcuts]]; for older users, they are at [[TCSH Shortcuts]]. In UNIX, type | Dr. G has created two pages describing some potentially handy UNIX shortcuts that you can add to your own accounts. For newer users, these are at [[BASH Shortcuts]]; for older users, they are at [[TCSH Shortcuts]]. In UNIX, type | ||
echo $SHELL | echo $SHELL | ||
to see which you should use. | to see which you should use. | ||
− | + | --> | |
===Connection Time Out=== | ===Connection Time Out=== | ||
− | *Teer machines now time out after 10 minutes of inactivity. The easiest way around this is to add the following line to the end of your .bashrc file or .cshrc file in your main CIFS directory. First, log in to a Teer machine and type | + | *Teer machines now time out after 10 minutes of inactivity. The easiest way around this is to start the program '''xeyes''' when you first log in; type |
+ | xeyes & | ||
+ | at the command prompt to get it to start. You can minimize this window, but do not close it. For whatever reason, the program will keep your session active! | ||
+ | <!-- | ||
+ | add the following line to the end of your .bashrc file or .cshrc file in your main CIFS directory. First, log in to a Teer machine and type | ||
echo $SHELL | echo $SHELL | ||
If the result is /bin/tcsh, edit the .cshrc file; if the result is /bin/bash, edit the .bashrc file. Here's the code to add: | If the result is /bin/tcsh, edit the .cshrc file; if the result is /bin/bash, edit the .bashrc file. Here's the code to add: | ||
Line 16: | Line 21: | ||
This code will start the <code>xeyes</code> program in the background, but will put it off screen so you will not actually see it. When you close the terminal or PuTTY window, <code>xeyes</code> will close as well. | This code will start the <code>xeyes</code> program in the background, but will put it off screen so you will not actually see it. When you close the terminal or PuTTY window, <code>xeyes</code> will close as well. | ||
**Note 2: if you use this, but you use shell escapes (for instance, the ! in MATLAB), the xeyes process will run each time... Meaning you could have thousands of eyes watching you from off-screen, thus significantly slowing things down. | **Note 2: if you use this, but you use shell escapes (for instance, the ! in MATLAB), the xeyes process will run each time... Meaning you could have thousands of eyes watching you from off-screen, thus significantly slowing things down. | ||
− | + | --> | |
− | + | ||
=== Printing from LaTeX Documents === | === Printing from LaTeX Documents === | ||
Due to an error in okular/CIFS and a missing program for evince, the process for actually printing a LaTeX document has changed slightly. Further documentation coming soon but the summary is: | Due to an error in okular/CIFS and a missing program for evince, the process for actually printing a LaTeX document has changed slightly. Further documentation coming soon but the summary is: | ||
Line 27: | Line 32: | ||
=== Others === | === Others === | ||
− | Anything of urgent concern will go here. Also see [http://oit.duke.edu/service-outages/ OIT Alerts] | + | Anything of urgent concern will go here. Also see [http://oit.duke.edu/service-outages/ OIT Alerts] for more information about possible outages. |
− |
Latest revision as of 17:30, 12 August 2015
Connection Time Out
- Teer machines now time out after 10 minutes of inactivity. The easiest way around this is to start the program xeyes when you first log in; type
xeyes &
at the command prompt to get it to start. You can minimize this window, but do not close it. For whatever reason, the program will keep your session active!
Printing from LaTeX Documents
Due to an error in okular/CIFS and a missing program for evince, the process for actually printing a LaTeX document has changed slightly. Further documentation coming soon but the summary is:
- latex file.tex
- dvips -t letter file.dvi
- evince file.ps &
Now, any time you want to re-process the file, you need to run both latex and dvips on it to get a new version of the ps file. Fortunately, evince will load any new ps file that comes up. You can then print from evince without any troubles. Admittedly, one more run is required but at least it works!
Others
Anything of urgent concern will go here. Also see OIT Alerts for more information about possible outages.