Sponsored Content
Special Forums IP Networking how to install ssh service in linux Post 302348521 by pludi on Friday 28th of August 2009 01:26:25 PM
Old 08-28-2009
The missing entry is a sign for an install gone wrong (although I'm not sure which step is responsible for that). It was possibly caused by the network issue you mentioned. But as long as you add those lines, it won't cause a problem later on.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ssh install

hi , i am trying to install ssh on solaris8 i have downloaded openssh. if anyone have installed openssh before , i like to know if there are anything else needed to install it. Some web sites says you need zlib and so on. i am confused. (1 Reply)
Discussion started by: oppai
1 Replies

2. Solaris

could not able to start the ssh service plz suggest

Hi Gurus I could not able to start the ssh service plz suggest root@bics-uatsrvr-01 # svcs -x ssh svc:/network/ssh:default (SSH server) State: offline since Thu May 28 04:12:02 2009 Reason: Service svc:/system/filesystem/usr:default is not running because a method failed. ... (1 Reply)
Discussion started by: girish.batra
1 Replies

3. Web Development

hosting service that allow me to compile and install my own apache

Is there any cheap hosting service that allow me to compile and install my own apache and php ? thanks (1 Reply)
Discussion started by: aneuryzma
1 Replies

4. UNIX for Dummies Questions & Answers

Problem with the SSH & Telnet Service

Hi gurus of Unix, I am newby in Unix, I need to Know the following. How I know if SSH & Telnet service is UP in Solaris? Please I appreciate your answer Regard Andres (2 Replies)
Discussion started by: andresguillen
2 Replies

5. Solaris

ssh service location on Solaris 8

Hi where can i find the ssh service on solaris 8 if "sshd" it is not available on /etc/init.d? i want to restart the service. i did a "which" and i found this. is this the right path? i want to double check since this is a prod server. bash-2.03# which sshd /usr/sbin/sshd Thanks (4 Replies)
Discussion started by: hrist
4 Replies

6. Programming

doing a socket connection using ssh service

Trying to establish a socket connection using ssh service - but want to use different login name for ssh than what currently logged in as - if under shell know to use ssh -l <login-name> host - however - not sure how to tell o.s. to use different login name when use connect command (2 Replies)
Discussion started by: clcoh11
2 Replies

7. Solaris

Helpme !! ssh service in maintenance mode

Hi Guys, Virtual Machine - Solaris 10 ssh service is in maintenance mode, when i tried to disable it it got disabled but when i enabling it ( svcadm enable ssh) it is coming in maintenance mode...... Pls help (10 Replies)
Discussion started by: saurabh84g
10 Replies

8. UNIX for Beginners Questions & Answers

Allow AD service account SSH to Linux systems without 2FA

I have Windows AD server and all of the linux computers are joined to AD. Recently, 2FA has been activated, I wish to exclude some of the domain service accounts from 2FA # less /etc/pam_radius_acl.conf sshd:* # /etc/pam.d/sshd auth required pam_sepermit.so auth requisite... (0 Replies)
Discussion started by: davidpar007
0 Replies
DH_INSTALLMAN(1)						     Debhelper							  DH_INSTALLMAN(1)

NAME
dh_installman - install man pages into package build directories SYNOPSIS
dh_installman [debhelperoptions] [manpage...] DESCRIPTION
dh_installman is a debhelper program that handles installing man pages into the correct locations in package build directories. In compat 10 and earlier, this program was primarily for when upstream's build system does not properly install them as a part of its install step (or it does not have an install step). In compat 11 and later, it supports the same features of dh_install(1) and has the advantage that it respects the nodoc build profile (unlike dh_install(1)). Even if you prefer to use dh_install(1) for installing the manpages, dh_installman can still be useful for converting the manpage encoding to UTF-8 and for converting .so links (as described below). However, that part happens automatically without any explicit configuration. You tell dh_installman what man pages go in your packages, and it figures out where to install them based on the section field in their .TH or .Dt line. If you have a properly formatted .TH or .Dt line, your man page will be installed into the right directory, with the right name (this includes proper handling of pages with a subsection, like 3perl, which are placed in man3, and given an extension of .3perl). If your .TH or .Dt line is incorrect or missing, the program may guess wrong based on the file extension. It also supports translated man pages, by looking for extensions like .ll.8 and .ll_LL.8, or by use of the --language switch. If dh_installman seems to install a man page into the wrong section or with the wrong extension, this is because the man page has the wrong section listed in its .TH or .Dt line. Edit the man page and correct the section, and dh_installman will follow suit. See man(7) for details about the .TH section, and mdoc(7) for the .Dt section. If dh_installman seems to install a man page into a directory like /usr/share/man/pl/man1/, that is because your program has a name like foo.pl, and dh_installman assumes that means it is translated into Polish. Use --language=C to avoid this. After the man page installation step, dh_installman will check to see if any of the man pages in the temporary directories of any of the packages it is acting on contain .so links. If so, it changes them to symlinks. Also, dh_installman will use man to guess the character encoding of each manual page and convert it to UTF-8. If the guesswork fails for some reason, you can override it using an encoding declaration. See manconv(1) for details. From debhelper compatibility level 11 on, dh_install will fall back to looking in debian/tmp for files, if it does not find them in the current directory (or wherever you've told it to look using --sourcedir). FILES
debian/package.manpages Lists man pages to be installed. OPTIONS
-A, --all Install all files specified by command line parameters in ALL packages acted on. --language=ll Use this to specify that the man pages being acted on are written in the specified language. --sourcedir=dir Look in the specified directory for files to be installed. This option requires compat 11 or later (it is silently ignored in compat 10 or earlier). Note that this is not the same as the --sourcedirectory option used by the dh_auto_* commands. You rarely need to use this option, since dh_installman automatically looks for files in debian/tmp in debhelper compatibility level 11 and above. manpage ... Install these man pages into the first package acted on. (Or in all packages if -A is specified). EXAMPLES
An example debian/manpages file could look like this: doc/man/foo.1 # Translations doc/man/foo.da.1 doc/man/foo.de.1 doc/man/foo.fr.1 # NB: The following line is considered a polish translation # of "foo.1" (and not a manpage written in perl called "foo.pl") doc/man/foo.pl.1 # ... NOTES
An older version of this program, dh_installmanpages(1), is still used by some packages, and so is still included in debhelper. It is, however, deprecated, due to its counterintuitive and inconsistent interface. Use this program instead. SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHOR
Joey Hess <joeyh@debian.org> 11.1.6ubuntu2 2018-05-10 DH_INSTALLMAN(1)
All times are GMT -4. The time now is 07:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy