Sponsored Content
Full Discussion: Suspicious file
Operating Systems AIX Suspicious file Post 302503166 by zxmaus on Wednesday 9th of March 2011 08:56:48 PM
Old 03-09-2011
most likely this file is not updated ever by a ML/TL - so you keep what you had during base install of the OS - and when you installed different versions of the OS than you just have a slightly different version of this ?

Regards
zxmaus
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How do I search my dot files for suspicious text?

My company Unix guru enabled fortune in my .login (dot login?) file. When i asked him how he did it he told me to search my dot files for "suspicious" text. He wants me to learn more about all of the dot files. (1 Reply)
Discussion started by: noobie_doo
1 Replies

2. Shell Programming and Scripting

Match list of strings in File A and compare with File B, C and write to a output file in CSV format

Hi Friends, I'm a great fan of this forum... it has helped me tone my skills in shell scripting. I have a challenge here, which I'm sure you guys would help me in achieving... File A has a list of job ids and I need to compare this with the File B (*.log) and File C (extend *.log) and copy... (6 Replies)
Discussion started by: asnandhakumar
6 Replies

3. Shell Programming and Scripting

Compare 2 text file with 1 column in each file and write mismatch data to 3rd file

Hi, I need to compare 2 text files with around 60000 rows and 1 column. I need to compare these and write the mismatch data to 3rd file. File1 - file2 = file3 wc -l file1.txt 58112 wc -l file2.txt 55260 head -5 file1.txt 101214200123 101214700300 101250030067 101214100500... (10 Replies)
Discussion started by: Divya Nochiyil
10 Replies

4. Shell Programming and Scripting

Shell script (sh file) logic to compare contents of one file with another file and output to file

Shell script logic Hi I have 2 input files like with file 1 content as (file1) "BRGTEST-242" a.txt "BRGTEST-240" a.txt "BRGTEST-219" e.txt File 2 contents as fle(2) "BRGTEST-244" a.txt "BRGTEST-244" b.txt "BRGTEST-231" c.txt "BRGTEST-231" d.txt "BRGTEST-221" e.txt I want to get... (22 Replies)
Discussion started by: pottic
22 Replies
DH_INSTALLDOCS(1)						     Debhelper							 DH_INSTALLDOCS(1)

NAME
dh_installdocs - install documentation into package build directories SYNOPSIS
dh_installdocs [debhelperoptions] [-A] [-Xitem] [file...] DESCRIPTION
dh_installdocs is a debhelper program that is responsible for installing documentation into usr/share/doc/package in package build directories. FILES
debian/package.docs List documentation files to be installed into package. debian/copyright The copyright file is installed into all packages, unless a more specific copyright file is available. debian/package.copyright debian/package.README.Debian debian/package.TODO Each of these files is automatically installed if present for a package. debian/README.Debian debian/TODO These files are installed into the first binary package listed in debian/control. Note that README.debian files are also installed as README.Debian, and TODO files will be installed as TODO.Debian in non-native packages. debian/package.doc-base Installed as doc-base control files. Note that the doc-id will be determined from the Document: entry in the doc-base control file in question. debian/package.doc-base.* If your package needs to register more than one document, you need multiple doc-base files, and can name them like this. OPTIONS
-A, --all Install all files specified by command line parameters in ALL packages acted on. -Xitem, --exclude=item Exclude files that contain item anywhere in their filename from being installed. Note that this includes doc-base files. --link-doc=package Make the documentation directory of all packages acted on be a symlink to the documentation directory of package. This has no effect when acting on package itself, or if the documentation directory to be created already exists when dh_installdocs is run. To comply with policy, package must be a binary package that comes from the same source package. debhelper will try to avoid installing files into linked documentation directories that would cause conflicts with the linked package. The -A option will have no effect on packages with linked documentation directories, and copyright, changelog, README.Debian, and TODO files will not be installed. (An older method to accomplish the same thing, which is still supported, is to make the documentation directory of a package be a dangling symlink, before calling dh_installdocs.) file ... Install these files as documentation into the first package acted on. (Or in all packages if -A is specified). EXAMPLES
This is an example of a debian/package.docs file: README TODO debian/notes-for-maintainers.txt docs/manual.txt docs/manual.pdf docs/manual-html/ NOTES
Note that dh_installdocs will happily copy entire directory hierarchies if you ask it to (similar to cp -a). If it is asked to install a directory, it will install the complete contents of the directory. Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHOR
Joey Hess <joeyh@debian.org> 9.20120909 2011-09-12 DH_INSTALLDOCS(1)
All times are GMT -4. The time now is 06:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy