Sponsored Content
Full Discussion: Host Name for PuTTY
Top Forums UNIX for Dummies Questions & Answers Host Name for PuTTY Post 302239434 by oxoxo on Tuesday 23rd of September 2008 03:54:39 PM
Old 09-23-2008
Host Name for PuTTY

im using the PuTTY configuration and i need a host name!

something that will give a prompt similar to this:

jdoe@theHostName.whatever.net or .com or .org ( im sure your familar )

then i need to login ( hopefully at the website ) and get this upon login:

[jdoe@theWebsite userName]$


i need this..
 

10 More Discussions You Might Find Interesting

1. IP Networking

QNX host cannot ping SCO host, vice versa

The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot (2 Replies)
Discussion started by: gavon
2 Replies

2. UNIX for Advanced & Expert Users

host alias not working: host not found

Hello, I am working on HP-UX , and in the /etc/hosts file we have setup an alias: aa.bb.cc.dd devmach2.unix.org devmach2 devma2v The alias devma2v does not work. Error when pinging devma2v ping: unknown host devma2v For devmach2 the ping works fine , returning the correct IP... (4 Replies)
Discussion started by: FunnyCats
4 Replies

3. Solaris

How to delete the files from local host to remote host

Hi all, i am copying .gz files from production server to development server using "scp" command.my requirement is after copying .gz files i want to delete old .gz files(two days back) in development server from production server. like this way i need to delelte .log ,.z and .dmp files... (3 Replies)
Discussion started by: krishna176
3 Replies

4. UNIX for Dummies Questions & Answers

PuTTY <Host Name Issue>

Hi, I'm Windows XP, and im running a PuTTY .exe file from chiark.greenend.org and i do not have the puttyTel .exe file. To obtain putty i got that address from the 'Visual Quickstart Guide' for UNIX ofcourse. After i've followed their instructions; being: "Type: 'frazz.raycomm.com' into the... (8 Replies)
Discussion started by: oxoxo
8 Replies

5. Shell Programming and Scripting

running commands to remote host from centralized host

Gurus/Experts We have a centralized UNIX/Solaris server from where we can actually ssh to all other UNIX/Solaris servers...I need to write a script that reside on this centerlized server and do FileSystem monitoring (basically run df -h or -k) of other remote servers and then send an email to me... (6 Replies)
Discussion started by: anjum.suri
6 Replies

6. UNIX for Advanced & Expert Users

Help! How to find the local host after few ssh hops to remote host???

I do a ssh to remote host(A1) from local host(L1). I then ssh to another remote(A2) from A1. When I do a who -m from A2, I see the "connected from" as "A1". => who -m userid pts/2 2010-03-27 08:47 (A1) I want to identify who is the local host who initiated the connection to... (3 Replies)
Discussion started by: gomes1333
3 Replies

7. UNIX for Dummies Questions & Answers

Transfer large number of files host to host

Hello.... I have two servers, one has an empty / and the other has a subdirectory with a large number (4 gig) with many, many files. I need a way to transfer the files en masse from the server with the large number of files to the one that is essentially blank. I don't have space on the used... (16 Replies)
Discussion started by: blaine.miller
16 Replies

8. Red Hat

Menu system for terminal like Putty for host /ip list

Is there a way to create a menu in Gnome terminal to have a list of hosts with ip's like in Putty on Windows? (2 Replies)
Discussion started by: jlouki01
2 Replies

9. Solaris

Need to recover/move diskgroup from failed host to another host

Hi All I am having VxVm on two Solaris hosts. host1 is using disk group dgHR. right now this server went down due to hardware fault. Not I need to import this dgHR into host2 server. Please let me know the procedure for the same. (1 Reply)
Discussion started by: amity
1 Replies

10. UNIX for Advanced & Expert Users

"Network error: No route to host" While connecting guest RHEL4 using putty

Hi, I have installed RHEL4 using vmware workstation.. Host OS: Windows XP Guest OS: RHEL4 Pls refer step 17 & 18 in below link... ORACLE-BASE - Red Hat Enterprise Linux 4 and Centos 4 Installation 1) If i choose to assign IP automatically (using DHCP) means, i am able to connect RHEL4... (3 Replies)
Discussion started by: thomasraj87
3 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)
All times are GMT -4. The time now is 09:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy