10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
I have a problem with ftp execution within unix environment.
I'd like to get files on remote and delete them later, but here is too crowd so I can accidentally delete some files. Can I delete only the files I can get to the local folder? I can ask this question with a different... (14 Replies)
Discussion started by: attillam
14 Replies
2. Shell Programming and Scripting
Hi,
Given addresses of 2 remote machines, using a shell script is it possible to
get the state of running processes in "src"
stop all the processes in "src"
exit out of "src"
ssh into "dest"
resume the state of executing processes captured in step 1 in "dest"
Assumption:
"src" is... (3 Replies)
Discussion started by: Saeya Darsan
3 Replies
3. Programming
Hi gurus,
I have a requirement where I need to remotely run a perl script as another user.
Running the script locally as the required user is fine, however I need to su with the script due to filesystem permission issues. I do not want to update permissions on the remote server due to security... (5 Replies)
Discussion started by: melias
5 Replies
4. Cybersecurity
If a user execute commands remotely over ssh : $ ssh USERNAME@SERVER COMMANDSHow the SERVER administrator can log those COMMANDS executed in a "not a tty" session ?
I searched for my question and get the following suggestions:Anybody give help how to do this ? what the content of "/bin/bash "... (1 Reply)
Discussion started by: new0h
1 Replies
5. UNIX for Dummies Questions & Answers
Hello, I'm new to scripting so, sorry if this is a dumb question. What's the best way to execute a .sh file remotely? I want to log into server "b" from server "a" & run a script. "./scriptname.sh". At this point, all I'm looking to do is a simple ls -la > output.txt within the script to capture... (3 Replies)
Discussion started by: crunch10c
3 Replies
6. Shell Programming and Scripting
does anyone know how can i execute a script which i locally run as " . /etc/local/host/src.srvr -D ."
need to execute above command in rexec command. if i put the command as it is it does not run. Sorry but i am naive in scripting. Thanks
rexec sgplqim -l vau -n '
' (0 Replies)
Discussion started by: NK4U
0 Replies
7. Shell Programming and Scripting
Hi folks
I am working on a script which lists files of a specific pattern on a remote m/c and tar&zip them to another remote m/c via a centralized server.
M/C details:
remote1 - OSF1 vayu V5.1 2650 alpha
remote2 - cygwin based windows server
central - SunOS phys-chenab 5.8... (2 Replies)
Discussion started by: royalbull
2 Replies
8. Shell Programming and Scripting
We have multiple Unix servers and a particular command can only be executed in one of the box from a specific path. I have password-less ssh set up for all the boxes. I am unsure the command to use to execute that particular command from any other box. To be specific say program named _my_exe_ can... (4 Replies)
Discussion started by: uunniixx
4 Replies
9. AIX
good morning
I would like copy and execute a shell script on a remote server
telnet is not autorize, so i use ssh:
scp to copy and ssh to execute
But with the scp, the permissions are not saved and the file 's permission on the remote server is r--r--r-- , so i can't execute it
Can you help... (2 Replies)
Discussion started by: pascalbout
2 Replies
10. Shell Programming and Scripting
Hi everybody,
sorry if the question will be too trivial for some of you, but I'm not a unix shell programmer expert.
I need to write a script that allows me to rlogin to another machine, check the load (cpu and mem usage) of the new machine, start a process (that will run in the background) and... (5 Replies)
Discussion started by: ragmelo
5 Replies
MAVEN(1) User Commands MAVEN(1)
NAME
Maven - Cleans a POM file.
SYNOPSIS
mh_cleanpom [option]... [pom] [target] [pom-props]
DESCRIPTION
Cleans the POM and prepare it for inclusion in the Maven repository. Also extracts some information from the POM.
debian/maven.rules is used to alter the version properties for the library and its dependencies.
Where
[pom] is the location of the POM file to clean.
Default to pom.xml or debian/pom.xml
[target] is where the cleaned POM is written to.
Default to debian/.mh/pom.xml
[pom-props] is where the POM properties file will be written.
Default to debian/.mh/pom.properties
OPTIONS
-h --help: show this text
-V --version: show the version
-p<package> --package=<package>: name of the Debian package which
will contain this POM file
-h --has-package-version: flag that indicates that this POM has the
same version as the package, this helps packagers of depending packages
-o --no-parent: don't inherit from a parent POM
-k --keep-pom-version: keep the original version of the POM 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
--keep-elements=<elem1,elem2>: keep the elements listed here
even if they are normally removed by the clean operation. Such elements are build,reports,reporting,prerequisites,profiles.
-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
Description:
Cleans a Maven POM and prepare it for inclusion in the Debian repository for Maven.
The POM will be normalised, and its parent tag removed if the option --no-parent is given. The version will be replaced by 'debian',
unless a special rule applies (see below the discussion about rules). Build, profiles and other build time only sections of the POM
will be stripped.
If versions are given for a dependency, this version will be replaced by the 'debian' version, or a rule can be given to use a cus-
tom version
You can modify those defaults with the help of the rules file. This file should contain the lines with the format: <groupId> [arti-
factId] [type] [version] [classifier] [scope] where groupId, artifactId, type, version, classifier and scope can be the explicit
attribute to match, or can contain a wildcard (*) for generic matches.
Each one of those elements can also be a replace rule, of the form s/<regex>/<replace>/ where regex is a regular expression, and
replace is the replacement. Substitution groups $1 $2... can be used in the replacement if capture groups () have been used in the
regex.
The first element is mandatory (groupId), but you can ignore the elements on the right hand side. If the scope is missing, then any
scope is matched and left unchanged. If the version is missing, then any version will be replaced with 'debian'. If type is miss-
ing, then any type is matched and left unchanged. If artifactId is missing, then any artifactId is matched and left unchanged.
You can also have comments in this file, it should be a line starting with #
Example of a rules file:
s/commons-(.*)/org.apache.commons.commons$1/ org.itext * * s/1..*/1.x/ org.itext * * s/2..*/2.x/ # use the alpha version of
plexus-container-default org.codehaus.plexus plexus-container-default jar s/1.0-alpha.*/1.0-alpha/
This rules file does the following: - all groupIds starting with commons- will have - org.apache.commons. prefixed to them - any
artifact in the org.itext group with a version number starting
with 1. will use the 1.x version
- any artifact in the org.itext group with a version number starting
with 2. will use the 2.x version
- the jar with groupId=org.codehaus.plexus and
artifactId=plexus-container-default and a version starting with 1.0-alpha- will use the 1.0-alpha version
The default rule (* * * s/.*/debian/ *) replaces any version number with the 'debian' version and always applies last if there was
no other matches. Another default rule (* * maven-plugin * *) keep the version for all plugins as the plugin mechanism requires a
version in Maven.
Any rules given on the command line (using -R/--extra-rule, -U/--extra-published-rule or -I/--extra-ignore-rule) are applied in the
order given, in between the rules given in the rules file (if any) and the default rules.
See also: mh_installpom(1), mh_installpoms(1)
Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)