To my knowledge you'll have to manually source the rc file in each running instance of the shell.
If you want to be clever, and anticipate doing this often enough, you could put the following command into your .bashrc file:
Once that is set in a running instance of bash, you then only need to send a SIGUSR1 (16) to the process and it will resource the .bashrc file. You could write a small script that susses out all of your running login/interactive shells and executes the necessary kill -16 command. You could pick another signal, but this seems just fine for this case.
Hope this helps some.
Last edited by agama; 05-09-2011 at 11:46 PM..
Reason: typo
Hi, I am working in huge environment, I do type commands from my terminal window repeadly in all same setup unix environments. I am looking some kind of a terminal emulator or some simple program that will help me?
basically if type command like 'ls' in one unix terminal window it should echo... (5 Replies)
I just wondering if there are ways to open multiple virtual terminal to a single LPAR.
After I have use putty to login to the VIOS. I will use mkvt -id <LPAR id> to open console but if my friend want to open 2 second one, it will say, VT already connected.
IS there a way to work this around ? ... (1 Reply)
I have written a simple script to show battery life remaining. I would like to be able to quickly view it with a predefined keybinding or launcher.
xterm -e scriptname should do the trick but the xterm closes when the script finishes, not giving me chance to read the output. How can I keep... (3 Replies)
OK this is a bit messy.
I run Fedora with gnome on a compiz desktop, I have a script (userstart) that opens my 'standard' environment for all my machines when I login. userstart flips to a specific workspace and then opens the required applications in that workspace then flips to the next... (2 Replies)
hi,
how to write shell script that runs different commands(like:ls,ps,ls-l) in differnt terminals(each command should run in different terminal).
my main motive is to run different 'c' program exe's available in different locations in different terminals.
thanks
sai (2 Replies)
Hi All ,
i am trying to create an alias to open a new gnome-terminal and run some commands in each tab & to have a specific name for each tab
i am using csh ,
tried this command
gnome-terminal --tab -t "s1" --tab -t "s2" --tab -t "s3" --tab -t "s4"
it opened 4 tabs but the title didn't... (0 Replies)
Discussion started by: Assem
0 Replies
LEARN ABOUT REDHAT
pam_console
pam_console(8) System Administrator's Manual pam_console(8)NAME
pam_console - control permissions for users at the system console
SYNOPSIS
session optional /lib/security/pam_console.so
auth required /lib/security/pam_console.so
DESCRIPTION
pam_console.so is designed to give users at the physical console (virtual terminals and local xdm-managed X sessions by default, but that
is configurable) capabilities that they would not otherwise have, and to take those capabilities away when the are no longer logged in at
the console. It provides two main kinds of capabilities: file permissions and authentication.
When a user logs in at the console and no other user is currently logged in at the console, pam_console.so will change permissions and own-
ership of files as described in the file /etc/security/console.perms. That user may then log in on other terminals that are considered
part of the console, and as long as the user is still logged in at any one of those terminals, that user will own those devices. When the
user logs out of the last terminal, the console may be taken by the next user to log in. Other users who have logged in at the console
during the time that the first user was logged in will not be given ownership of the devices unless they log in on one of the terminals;
having done so on any one terminal, the next user will own those devices until he or she has logged out of every terminal that is part of
the physical console. Then the race can start for the next user. In practice, this is not a problem; the physical console is not gener-
ally in use by many people at the same time, and pam_console.so just tries to do the right thing in weird cases.
ARGUMENTS
debug turns on debugging
allow_nonroot_tty
gain console locks and change permissions even if the TTY's owner is not root.
permsfile=filename
tells pam_console.so to get its permissions database from a different file than /etc/security/console.perms
fstab=filename
tells pam_console.so to read the table of configured filesystems from a file other than /etc/fstab when scanning permsfile. This
file is used to map directories to device names.
FILES
/var/run/console.lock
/var/run/console/
/etc/security/console.apps
/etc/security/console.perms
SEE ALSO console.perms(5)console.apps(5)
/usr/doc/pam*/html/index.html pam_console_apply(8)
/usr/doc/pam*/html/index.html
BUGS
Let's hope not, but if you find any, please report them via the "Bug Track" link at http://bugzilla.redhat.com/bugzilla/
AUTHOR
Michael K. Johnson <johnsonm@redhat.com>
Red Hat 2000/7/11 pam_console(8)