05-27-2010
just read the rules and don't use words like "urgent" in your title.
10 More Discussions You Might Find Interesting
1. Programming
Can I do it like this?
if (strcmp(argv, "history")==0)
{
argv = "10";
execvp(argc,argv);
}
actually, it doesn't work,
How can I modify it?
Thanks (17 Replies)
Discussion started by: zhshqzyc
17 Replies
2. UNIX for Advanced & Expert Users
hi
I want to know how to save all the command used by all the used under a particular root with the time stamp in a file.
Eg:
User Name: UX10
Time: 10:56
Command: LS
User Name: UX23
Time: 10:59
Command: MORE abc.txt
-Anand (2 Replies)
Discussion started by: anandtharani
2 Replies
3. UNIX for Dummies Questions & Answers
Like the topic says, does anyone know if it is possible to check to see when an FTP only user has logged in? Because the shell is /bin/false and they are only using FTP to access the system doing a "finger" or "last" it says they have never logged in.
Is there a way to see when ftp users log in... (1 Reply)
Discussion started by: LordJezo
1 Replies
4. Shell Programming and Scripting
dear all ,
I m new to shell programming and I need your help.
Actually i want to keep track of all the commands executed in a bash prompt of users ,
very much in same manner as it is displayed when we run "history" command.
now the users are smart enough as they delete their history by... (6 Replies)
Discussion started by: xander
6 Replies
5. AIX
Hi
Does anybody know if there is a way in AIX 5.3 to track how a user was logged off? For instance where the user typed exit, hit crtl D, shell process was killed, etc.
I know of the last log entries but this just shows a users login time and duration. I also tried syslog but I only get login... (5 Replies)
Discussion started by: kimyo
5 Replies
6. UNIX for Advanced & Expert Users
Hi,
I have a unix server and I am concerned about the security on that server.
I would like to be able to write a script that records all the commands that were typed at the command prompt before the user calls the 'history -c' command and deletes all the history.
I was thinking about firing or... (7 Replies)
Discussion started by: mishkamima
7 Replies
7. AIX
Recently we've had a couple user accounts mysteriously disappear. Is there any way to track these accounts and determine who/how they were deleted? (2 Replies)
Discussion started by: Sk0glund
2 Replies
8. UNIX for Dummies Questions & Answers
Hi, i suddenly realized that a directory is deleted unfortunately there are many user have pervilages on this directory
is there a way to track the user who delete this directory
or atleast from now can i enable something so that i can track from now
I think there is way from... (2 Replies)
Discussion started by: crackgeek
2 Replies
9. UNIX for Dummies Questions & Answers
Hi All
Please can you help me with the following issue:
A certain vendor installed an application in which for a user to log in; the user must use a user created/predefined by the application. And because this application has more than one user its difficult to track who did what and when,... (6 Replies)
Discussion started by: fretagi
6 Replies
10. UNIX for Advanced & Expert Users
Hi All
We have a job which writes files to a server at a particular time. The files will be created by a particular user ID
Today, during the execution of the job, it created a file to the server and the file sat on the server for sometime, but was deleted immediately at the end of the... (4 Replies)
Discussion started by: sparks
4 Replies
LEARN ABOUT DEBIAN
mh_patchpoms
MAVEN(1) User Commands MAVEN(1)
NAME
Maven - Patches the POM files using the Maven dependency rules.
SYNOPSIS
mh_patchpoms [option]...
DESCRIPTION
Reads the file debian/$package.poms and tranform each POM file listed in the .poms file into a POM file using the Debian versions of the
libraries. Also keeps a backup of each POM file which can be restored with mh_unpatchpoms
OPTIONS
-h --help: show this text
-V --version: show the version
-p<package> --package=<package>: package to act on
-k --keep-pom-version: keep the original version of the POMs but,
convert all other versions in dependencies and plugins If there is a parent POM, keeps its version except when the parent is already
registered in the Maven repository
-e<version>, --set-version=<version>: set the version for the POM,
do not use the version declared in the POM file.
-r<rules> --rules=<rules>: path to the file containing the
rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules
-R<rule>, --extra-rule=<rule>: extra rule to apply when cleaning the POM
May occur multiple times, instead of or in addition to -r
-u<rules> --published-rules=<rules>: path to the file containing the
extra rules to publish in the property debian.mavenRules in the cleaned POM. Optional, the default location is debian/maven.pub-
lishedRules
-U<rule>, --extra-published-rule=<rule>: extra rule to publish
May occur multiple times, instead of or in addition to -u
-i<rules> --ignore-rules=<rules>: path to the file containing the
rules used to remove certain dependencies from the cleaned POM Optional, the default location is debian/maven.ignoreRules
-I<rule>, --extra-ignore-rule=<rule>: extra rule used to remove dependencies
from the transformed POM May occur multiple times, instead of or in addition to -i
-c<rules> --clean-ignore-rules=<rules>: path to the file containing the
rules use to remove certain dependencies from the cleaned POM, in addition to the ignore rules specified previously. This is useful
in situations such as when the Maven clean target requires more dependencies or plugins to ignore than the build target. All rules
defined in clean-ignore-rules will be added to the existing rules in ignore-rules. Optional, the default location is
debian/maven.cleanIgnoreRules
-s --no-rules: don't apply any rules for converting versions,
do not even convert versions to the default 'debian' version
--no-publish-used-rule: don't publish the rule used to transform
a POM's own attributes in debian.mavenRules
-d --debian-build: transform during a Debian build, which means that
some POM elements will be removed
-b --build-no-docs: if the build doesn't need to build documentation, use this
option to remove some POM elements (in particular plugins) which are useless here and may require extra dependencies and make the
packaging harder.
-m<repo root>--maven-repo=<repo root>: location of the Maven repository,
used to force the versions of the Maven plugins used in the current POM file with the versions found in the repository
-v --verbose: show more information while running
-n --no-act: don't actually do anything, just print the results
See also: mh_installpoms(1), mh_patchpom(1)
Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)