10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hi folks.
I'm using pssh to run commands on a cluster, (pis/Raspian/Jessie) but I'm opening a app that runs and runs and runs. It's quite helpful to vnc to a machine to make sure it's still running ok now and then, but they're basically left alone.
Of course when pssh runs a command it... (2 Replies)
Discussion started by: MuntyScrunt
2 Replies
2. Shell Programming and Scripting
Hi Friends,
Every I try to open a vi window, vim help.txt automatically opens evertime.
After doing ZZ or :q! also the same page opens automatically.
How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue.
Thanks... (3 Replies)
Discussion started by: sudiptabhaskar
3 Replies
3. UNIX for Beginners Questions & Answers
Hi Friends,
Every I try to open a vi window vim help.txt automatically opens evertime.
After doing ZZ or :q! also the same page opens automatically.
How to stop this? Is it machine specific ? Other users who are opening the same servers and files are not facing this issue.
Thanks... (1 Reply)
Discussion started by: sudiptabhaskar
1 Replies
4. Shell Programming and Scripting
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
5. Red Hat
Hello everyone. I want to create an alias of vi, so that everytime I use vi to edit something, it will open up a new terminal session, with the vi file that I want to edit. So for example if I enter:
sudo vi /etc/bashrc
This will open up a brand new terminal window, with the /etc/bashrc file... (1 Reply)
Discussion started by: Lost in Cyberia
1 Replies
6. Shell Programming and Scripting
Hi All,
Is it possible that Perl script open a webpage and when that webpage opens there is some text box in which data needs to be filled.The Perl script read the data from file and fill in that webpage. And after that click the submit button. (4 Replies)
Discussion started by: parthmittal2007
4 Replies
7. Linux
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)
Discussion started by: Bashingaway
2 Replies
8. IP Networking
My router has UPnP,how to make it work with ubuntu to automatically open ports
I try to open the following command " /sbin/iptables -I INPUT -d 0/0 -s 0/0 -p tcp --dport 21 -j ACCEPT" ,local only opens ,if i put the ip 192.168.1.68, it works correctly, if i`m put my external ip does not work,I... (9 Replies)
Discussion started by: dhalus
9 Replies
9. Solaris
Hi, Is there a way to open and arrange terminal windows automatically under CDE? For example, I want to open and arrange terminal windows like this:
|------------|
| TW TW TW |
| TW TW TW |
| TW TW TW |
|------------|
Thank you in advanced! (5 Replies)
Discussion started by: aixlover
5 Replies
10. Shell Programming and Scripting
Hi
I am trying to write a script to automatically use a predefined program to open a file according to its extension... But I don't know how to pass "programeta" ... :confused:
while ]; do
case $1 in
-pdf ) programeta="kpdf"
shift 1 ;;
... (1 Reply)
Discussion started by: pau
1 Replies
ttys(4) Kernel Interfaces Manual ttys(4)
NAME
ttys - Terminal control database file (Enhanced Security)
DESCRIPTION
Notes
The secure terminal database file, /etc/securettys, controls root logins for all security levels. The file is described in the securet-
tys(4) reference page.
By default, the enhanced security terminal control information is stored in database format (ttys.db). The information was formerly stored
in the ttys file and is converted to database format in an update installation. The convauth utility converts an existing ttys file to
database format.
The enhanced security terminal control database (ttys.db) contains an entry for each terminal or X displayname that can be used for logging
in. It supports wildcarding of the entire terminal name or displayname only. Authentication programs use information in the terminal con-
trol database to determine if a login is permitted on the specified terminal. Information from the device assignment database
(/etc/auth/system/devassign) can also affect terminal login permissions. Successful and unsuccessful login attempts on the terminal are
optionally recorded in the terminal control database, and the information can be used to disable terminal logins when breakin attempts are
suspected.
The /usr/tcb/bin/dxdevices GUI provides a way to create terminal control database entries and to alter the system default values for the
fields. The edauth utility can also be used to display and modify terminal control database entries.
A terminal control database entry consists of keyword field identifiers and values for those fields. If a necessary value is not specified
in an entry, a default value for the field is supplied from the system default file (/etc/auth/system/default). For more information on
the field format, see the authcap(4) reference page.
The following keyword field identifiers are supported: This field defines the terminal device name for the entry. The system expects that
terminal devices are in the /dev directory and therefore this prefix should not be specified. If the terminal entry describes the /dev/tty1
device, the t_devname field should contain tty1. This field is ignored if it is set in a template or in the default database. This field
contains the user ID of the last user who successfully logged in using the terminal device. This field is ignored if it is set in a tem-
plate or in the default database. This field is a time_t value that records the last successful login time to the terminal device. This
field is ignored if it is set in a template or in the default database. This field contains the user ID of the last user who unsuccess-
fully attempted to log in using the terminal device. This field is ignored if it is set in a template or in the default database. This
field is a time_t value that records the last unsuccessful login time to the terminal device. This field is ignored if it is set in a tem-
plate or in the default database. This field contains the user ID of the user who successfully logged in before the user identified in the
t_uid field. This represents the UID of the previous login session. This field is ignored if it is set in a template or in the default
database. This field is a time_t value that contains the system time of last logout associated with this terminal device. This value marks
the end of the previous login session associated with the user identified by t_prevuid. This field records the number of consecutive
unsuccessful login attempts to the terminal device. This field is ignored if it is set in a template or in the default database. This
field specifies the maximum number of consecutive unsuccessful login attempts permitted using the terminal before the terminal is locked.
Once the terminal is locked, it must be unlocked by an authorized administrator. This field is a time_t value that identifies the login
delay enforced by authentication programs between unsuccessful login attempts. This field is designed to slow the rate at which penetration
attempts on a terminal device can occur. This field indicates whether the terminal device has been administratively locked. This field is
manipulated by authorized administrators only. This field specifies the time interval in seconds after t_unsuctime to wait before ignoring
t_failures. Zero means never ignore t_failures. This field specifies the login time-out value in seconds. If a login attempt is initiated
by entering a user name at the login prompt but successful authentication is not completed within the time-out interval specified, the
login attempt is aborted. This field indicates that the entry is an X window display managed by rather than a terminal device. This field
is ignored if it is set in a template or in the default database.
EXAMPLES
The following example shows a typical terminal control database entry: console:t_devname=console:
:t_uid=jdoe:t_logtime#675430072:
:t_unsucuid=jdoe:t_unsuctime#673610809:
:t_prevuid=root:t_prevtime#671376915:
:chkent:
This entry is for the system console device, /dev/console. The most recent successful login session was for the user jdoe. The most recent
unsuccessful login attempt was also by user jdoe. Before the most recent successful login session, the root account was used to log in to
the console. The entry records the system time for the current successful login, the end of the previous successful login session, and the
time of the most recent unsuccessful login attempt.
FILES
Specifies the pathname of the database.
RELATED INFORMATION
Commands: login(1)
Functions: getprtcent(3)
Files: authcap(4), default(4), securettys(4) delim off
ttys(4)
