Sponsored Content
Full Discussion: Unix Security - SU logs
Operating Systems HP-UX Unix Security - SU logs Post 302340522 by TonyFullerMalv on Monday 3rd of August 2009 05:53:23 PM
Old 08-03-2009
There will be a manpage for the sulog file which will inform you of what each column is, I have not located an HP-UX manpage for it online, here is the Solaris one (no guarentee the formatting will be the same):
sulog man page
 

9 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Clear logs in unix sco 5.0.4

hi my name es juan i have sco open server 5.0.4 release i need clear the log files as wtmp thanks you very much (1 Reply)
Discussion started by: jtapia
1 Replies

2. HP-UX

Unix - Logs

Hi All, Can anybody tell me, how to trace out user access to the Unix Server Machine, (i,e) I want to find out the user who had executed some commands to alter the cron file. Regards Nag (3 Replies)
Discussion started by: nag_sundaram
3 Replies

3. UNIX for Dummies Questions & Answers

FTP Logs in Unix

Hi. Is there a way or command (other than netstat) in Unix to find out or get a list a users who FTP into a particular server? Like, say last 1000 users. I need to get the user ID (any info), who FTP to a particular server. netstat gives only the users who have an FTp session currently. ... (2 Replies)
Discussion started by: manisendhil
2 Replies

4. Linux

FTP Logs in Linux/Unix

Hi, I need to get a hostory of users who FTP into a server. How can I do it in Linux/Unix? Is there a command for this? I do not want to use netstat -a as it gives only the list of users who have a session currently on the server. Can this be done with the "last" command? Please do let me... (0 Replies)
Discussion started by: manisendhil
0 Replies

5. UNIX for Advanced & Expert Users

How to disable application level logs in Unix?

Hi, I'm working in an application and the related Java code and the envrionment is in Unix server. We are generating the log messages using loggers of Java.util.log . But, the logs are not getting generated in the log files. We feel that the people who developed the system might have done some... (6 Replies)
Discussion started by: kelangovan
6 Replies

6. UNIX for Advanced & Expert Users

How to view the unix logs in windows ??

Hi ! I have a FTP site, where I softlinked my server log file. Now I want to view the logs in IE as I do in unix Some kind of free tool should be there, Can somebody provide me a pointer. Thanks. (0 Replies)
Discussion started by: dashok.83
0 Replies

7. UNIX for Advanced & Expert Users

FTP Logs in Unix

Hi. Is there a way or command (other than netstat) in Unix to find out or get a list a users who FTP into a particular server? Like, say last 1000 users. I need to get the user ID (any info), who FTP to a particular server. netstat gives only the users who have an FTp session currently. ... (4 Replies)
Discussion started by: manisendhil
4 Replies

8. UNIX for Dummies Questions & Answers

File transmission logs in UNIX

Can any one give a explaination with examples on how to understand file transmission log files in Unix for inbound and outbound traffic. (1 Reply)
Discussion started by: ITDev01
1 Replies

9. UNIX for Dummies Questions & Answers

Problem with UNIX logs file

I'm working on Logs Management System. it requires from all Unix servers to send their logs files to a specific (IP, Port). Please help me to get the right conf on logs files to send them to that IP and port. Any suggestions are highly appreciated. :o:o (0 Replies)
Discussion started by: kinan adra
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 09:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy