Sponsored Content
Full Discussion: Automating Putty logins
Top Forums Shell Programming and Scripting Automating Putty logins Post 302475133 by Corona688 on Friday 26th of November 2010 02:59:05 PM
Old 11-26-2010
Putty can't remember passwords, and shouldn't remember passwords. But like any competent SSH client it can use shared keys. Here's some directions.

If you're not allowed to even download executables on that machine, you can do the key creation part on your own computer and just bring the files.
This User Gave Thanks to Corona688 For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Help with logins

Could someone please tell me what I would have to do so I can dial in to Solaris through a modem and login? Thanks in advance. Jomar (2 Replies)
Discussion started by: crispyco
2 Replies

2. UNIX for Dummies Questions & Answers

NVT logins

Hello again! Another thing came up the other day. I've noticed that a few of my "beloved" users who by the way, use NVT (Novell Virtual Terminal) to log in the server, when told to log off, press the power button to shut down their computer, instead of logging off as they should. As a result... (2 Replies)
Discussion started by: pappous
2 Replies

3. Shell Programming and Scripting

Logins-logouts

I want a script that checks the logins and logouts in a system.Is there a way to keep the logins and logouts in files and then compare them every e.g. 10 seconds? for tcsh. (1 Reply)
Discussion started by: aekaramg20
1 Replies

4. AIX

Limit logins to 1

Trying to limit 1 login per account... Setup: We have 2 auth logins, one to the AIX (telnet)then into a distribution mgmt software, the users do not have a shell to log into on the AIX itself, so placing a script such as: active=`who | awk '{printf",%s,\n",$1}' | grep ,$LOGNAME, | wc -l` ... (0 Replies)
Discussion started by: pheusion
0 Replies

5. UNIX for Dummies Questions & Answers

Linmit user logins

Hello everyone, traditionally a user can log in on more than one machine as much as they want. In AIX 4.3, Is there a way to make it so that if the user is already logged on, the system will not let them log on, therefor not run their logon profile script again? (limit the user to one machine at a... (1 Reply)
Discussion started by: raidzero
1 Replies

6. AIX

allow / deny root logins

Hello everyone I have to limit the root logins on my aix box (aix 5.3) I change the value on the /etc/security/user default (login and rlogin) change to false and add to root (rlogin and login = false) I tried in different ways but I got the same. Root still can login I try algo... (6 Replies)
Discussion started by: lo-lp-kl
6 Replies

7. Shell Programming and Scripting

Last two logins script

This is the contents of my file: donald.duck 12/07/2009 12:07:58 donald.duck 12/07/2009 12:17:36 donald.duck 12/07/2009 12:22:29 donald.duck 12/07/2009 12:26:39 donald.duck 12/07/2009 12:28:01 mickey.mouse 12/07/2009 12:48:49 mickey.mouse 12/07/2009 12:49:33 mickey.mouse 12/07/2009... (3 Replies)
Discussion started by: diallo0024
3 Replies

8. AIX

Alert on successfully logins

Hi, How difficult would it be to configure an alert on AIX that will inform me every time someone logs into the system? (1 Reply)
Discussion started by: bbbngowc
1 Replies

9. Solaris

User Logins

Is the below logins are needed in the machine..... nuucp , uucp ,smmsp , svctag , listen , webservd , ip ( We are not using printers), Can you help in these? Regards, kumar (3 Replies)
Discussion started by: rajeshkumarvg
3 Replies

10. Shell Programming and Scripting

Automating pbrun /bin/su not working, whenever manually it is working using putty

I am trying to automate a script where I need to use pbrun /bin/su but for some reason it is not passing thru the pbrun as my code below. . ~/.bash_profile pbrun /bin/su - content c h 1 hpsvn up file path I am executing this from an external .sh file that is pointing to this scripts file... (14 Replies)
Discussion started by: jorgejac
14 Replies
site-lib(5)							File Formats Manual						       site-lib(5)

NAME
site-lib - [Location of package directories] STANDARD LAYOUT
...somewhere in the filesystem hierarchy... | site-lib | +- (optional) stublibs +- (optional) postinstall +- (optional) postremove | +- package1 | | | +- META | +- archive files | +- interface definitions | +- package2 + : : packageN DESCRIPTION
Every installation of "findlib" has a default location for package directories, which is normally a directory called "site-lib". The loca- tion can be set by the configuration variables path (used to look up packages), and destdir (used to install new packages); see find- lib.conf. The name of a package is the name of the package directory. For example, if destdir=/usr/local/lib/ocaml/site-lib, the package p will be installed in the subdirectory /usr/local/lib/ocaml/site-lib/p. This subdirectory must contain the META file and all other files belonging to the package. Package names must not contain the '.' character. The variable destdir specifies the directory for new packages. You can only have one such directory at a time; but of course you can change this directory in findlib.conf. The command ocamlfind install puts new packages into this directory; it is recommended to use this command for installation because it ensures that the directory layout is right. For searching packages, findlib uses (only) the variable path which may name several locations to look at. For systems with DLL support another directory may exist: stublibs. If present, findlib will install DLLs into this directory that is shared by all packages at the same site-lib location. Findlib remembers which DLL belongs to which package by special files with the suffix ".owner"; e.g. for the DLL "dllpcre.so" there is another file "dllpcre.so.owner" containing the string "pcre", so findlib knows that the package "pcre" owns this DLL. It is not possible that a DLL is owned by several packages. If the stublibs directory does not exist, DLLs are installed regularly in the package directories like any other file. For special needs, a postinstall and/or a postremove script may be installed in the site-lib directory. These scripts are invoked after installation or removal of a package, respectively. ALTERNATE LAYOUT
...somewhere in the filesystem hierarchy... | site-lib | +- (optional) stublibs +- (optional) postinstall +- (optional) postremove | +- package1 | | | +- archive files | +- interface definitions | +- package2 + : : : packageN | metaregistry | +- META.package1 +- META.package2 + : META.packageN This is an alternate directory layout collecting all META files in one directory. You can configure this layout by setting path to the absolute location of metaregistry. Findlib recognizes that there are META files in this directory and uses them; it is not necessary to include site-lib into the path. In order to work, the META files must contain a directory directive pointing to the corresponding package directory that resides below site-lib. The command ocamlfind install copes with this layout, too. The variable destdir must contain the absolute location of site-lib, and the variable metadir must contain the absolute location of metaregistry. Note that ocamlfind install automatically adds a directory directive to the META file, so you need not do it manually. User Manual The findlib package manager for OCaml site-lib(5)
All times are GMT -4. The time now is 07:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy