Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Hostname lost when changing user Post 97589 by Pablo_BR on Tuesday 31st of January 2006 07:52:14 PM
Old 01-31-2006
Hostname issue

Man, you are a genius!

By giving this clue, of putting a temporary flag, I could detect the exact line which was bringing the problem.

The doc profile is cleared, but after placing some of these flags inside /etc/khsrc I could find the line and the wrong variable. Now I have changed it and it's ok now.

Thank you very much!
Pablo.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

what happen when changing Hostname?

I 'm using RH 7.2 Genome in the Network Configuration I change therer are two places one for static hostname for my machine and in DNS hostname I don't know what happen when restarting my PC when connecting using dialer I can't browse the Internet also I can't use sendmail .......Server timeout... (2 Replies)
Discussion started by: atiato
2 Replies

2. HP-UX

lost standart input after su - <user>

All, hope somebody can help here: wrote a small shell script running under root on //usr/bin/ksh no specialisties in the profile. Then the test script: ------------------------------------------- echo "Now we start, press any key..." read su - test -c "id | wc -l" 2>/tmp/x echo... (0 Replies)
Discussion started by: tamo2000
0 Replies

3. UNIX for Advanced & Expert Users

How to stop DHCP from changing hostname

Hi, greetings. I have installed OS 10 on sunfire 240. FOr now let dhcp to give IP address but it keeps chaning hostname. How do I stop this? thanks Jaya (3 Replies)
Discussion started by: vr76413
3 Replies

4. Solaris

changing ip and hostname on solaris

dears does any one know in steps how can i change ip and hostname on solaris (10 Replies)
Discussion started by: murad.jaber
10 Replies

5. UNIX for Dummies Questions & Answers

Changing IP & hostname

I have to do this twice. First, A) change IP address, subnet & default gateway. then a few days later B) change IP address again (same subnet & gateway) & hostname. (why twice? To get the vlan stuff out of the way in advance) what is the best way to do A? can all be done through... (5 Replies)
Discussion started by: LisaS
5 Replies

6. Solaris

changing hostname on Solaris 8 ?

hi, does anyone had experience changing hostname on Solaris 8 ? any idea how is it done ? (4 Replies)
Discussion started by: Exposure
4 Replies

7. Solaris

SVM - Metadevices are offline after changing hostname solaris x86

Hi , We are facing an issue on one of our solaris x86 server, After changing the hostname and a orderly reboot , all metadevices shows offline. please let us know the steps to restore back all metadevices to working state with this new hostname (3 Replies)
Discussion started by: karthick.sh
3 Replies

8. Solaris

New user: lost application manager

Dear all, I am a beginner with Solaris. I unfortunately remove the Application Manager from the Front Panel, and I really don't know how to put it again, or from where launch it... Could anyone help me? (1 Reply)
Discussion started by: avr
1 Replies

9. UNIX for Dummies Questions & Answers

How do I know my user@hostname ?

(8 Replies)
Discussion started by: wojeezy
8 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 03:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy