08-09-2019
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
When logged in as root if I type "env" there are a bunch of environment settings including one for CLASSPATH. However, I ran a cron script that ran this command "env > cronEnv". I noticed that the environment variables were entirely different inside the script. There wasn't even a CLASSPATH... (2 Replies)
Discussion started by: doublek321
2 Replies
2. UNIX for Dummies Questions & Answers
I've got an *extremely* simple script I want to run every minute:
#!/bin/sh
ping -c 1 192.168.1.20 > ~/onlinestatus.txt
So, the script is called "status", it's executable, and in the correct path, etc. In a terminal window (I'm using Mac OS X), I can type status, and it will create... (4 Replies)
Discussion started by: jmf77
4 Replies
3. AIX
hello
I use a script to give me the number of users, at each hour.
this script read a file where there is the number of users for each hour and for each month (so 12 files per year).
If i execute the script (root), it is ok, i have xxx users for each hour.
if I put the script in the cron... (1 Reply)
Discussion started by: pascalbout
1 Replies
4. Shell Programming and Scripting
guys
i have written a very simple script .it runs manually well.
but when i put it in cron,it doesn't give the desired output.
script looks like this:
#! /usr/bin/sh
#script for loading data in table using ctl file/Abhijeet K/08.07.2006
/svm_wl1/. .profile
cd... (5 Replies)
Discussion started by: abhijeetkul
5 Replies
5. Solaris
I want to cron one script which should run every second Thursday (in general Nth occurence of any day) of every month.
I am not getting the exact idea of doing this; Please guide.
Regards, (3 Replies)
Discussion started by: jaiankur
3 Replies
6. Shell Programming and Scripting
Good morning. I am searching for "how-to"'s for some particular questions:
1. How to write a script in HP-UX 11.
2. How to schedule a script.
3. How to "call" scripts from the original script.
4. How to su to another user from within a script.
This is the basics of what the... (15 Replies)
Discussion started by: instant000
15 Replies
7. Solaris
Dear All,
I have an assignment about collecting /var/adm/messages on each server running Solaris 9. All these servers will be installed with a script that collect all the messages in cron. All the messages will be collected by a single server.
I have a script to collect all the messages, but... (2 Replies)
Discussion started by: frankoko
2 Replies
8. Shell Programming and Scripting
This has to be the ultimate newbie question...
I have a script that works well. To run it, I cut and paste it into a putty session.
Is there a way to put the script into a file and just run that file -- like a DOS batch file?
I'd like to schedule the file to run daily.
Thanks,... (3 Replies)
Discussion started by: landog
3 Replies
9. UNIX for Dummies Questions & Answers
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
10. Shell Programming and Scripting
I have a script that require input from terminal at some point (either a,b or c)
How can I cron the script and automatically assume c as the input. (2 Replies)
Discussion started by: aydj
2 Replies
LEARN ABOUT SUSE
gitmodules
GITMODULES(5) Git Manual GITMODULES(5)
NAME
gitmodules - defining submodule properties
SYNOPSIS
$GIT_WORK_DIR/.gitmodules
DESCRIPTION
The .gitmodules file, located in the top-level directory of a git working tree, is a text file with a syntax matching the requirements of
git-config(1).
The file contains one subsection per submodule, and the subsection value is the name of the submodule. Each submodule section also contains
the following required keys:
submodule.<name>.path
Defines the path, relative to the top-level directory of the git working tree, where the submodule is expected to be checked out. The
path name must not end with a /. All submodule paths must be unique within the .gitmodules file.
submodule.<name>.url
Defines an url from where the submodule repository can be cloned.
submodule.<name>.update
Defines what to do when the submodule is updated by the superproject. If checkout (the default), the new commit specified in the
superproject will be checked out in the submodule on a detached HEAD. If rebase, the current branch of the submodule will be rebased
onto the commit specified in the superproject. If merge, the commit specified in the superproject will be merged into the current
branch in the submodule. This config option is overridden if git submodule update is given the --merge or --rebase options.
EXAMPLES
Consider the following .gitmodules file:
[submodule "libfoo"]
path = include/foo
url = git://foo.com/git/lib.git
[submodule "libbar"]
path = include/bar
url = git://bar.com/git/lib.git
This defines two submodules, libfoo and libbar. These are expected to be checked out in the paths include/foo and include/bar, and for both
submodules an url is specified which can be used for cloning the submodules.
SEE ALSO
git-submodule(1) git-config(1)
DOCUMENTATION
Documentation by Lars Hjemli <hjemli@gmail.com[1]>
GIT
Part of the git(1) suite
NOTES
1. hjemli@gmail.com
mailto:hjemli@gmail.com
Git 1.7.1 07/05/2010 GITMODULES(5)