| PLEX86 | ||
|
scripts after loggingAMERICA IN DANGER AMERICA IN DANGER! Secret Gas-Aerosol Rooms operated in US (in Philadelphia, Narberth, Lower Merion, PA) (in Wilmington and Newark, DE) (in Hampton... Sun and said: This depends on your shell. Check your man page if you're using something other than bash. bash (the standard shell on Linux) sources ~-.bashprofile when you log in via a console. Generally, .bashprofile checks to see if ~-.bashrc exists and then sources .bashrc . .bashrc is also sourced when you log in via a non-login shell. Generally, you want to put all your startup stuff in .bashrc, so it's always available. Keep in mind that sourcing .bashrc should *never* generate any output if the shell is non-interactive, or scp will break. You often see things like this: if $- != *i* ; then # Shell is non-interactive. Be done now! return fi ...at the top of .bashrc . You often set environment variables, aliases, and whatever shell functions you need within .bashrc as well. For insane amounts of detail, "man bash". NOTE: Doing this in a GUI is different. In KDE, you put scripts (or symlinks) in ~-.kde-Autostartso they'll be automatically executed whenever you log in to KDE. GNOME has something similar somewhere. HTH, -- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL
|
||||
Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||