9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi ,
I have scheduled the script using cron between 25-31 of the month.
My script will trigger the ETL job once file is available in Windows path between these days(every 2 hours between 26 - 30 of every month ).
So my question : "if the ETL job completes cron should stop the running the... (5 Replies)
Discussion started by: Jaganjag
5 Replies
2. Shell Programming and Scripting
The `bash` below uses the oldest folder in the specified directory and logs it. The goes though an analysis process and creates a log. My problem is that if there are 3 folders in the directory folder1,folder2,folder3, the bash is using folder2 for the analysis eventhough folder1 is the oldest... (0 Replies)
Discussion started by: cmccabe
0 Replies
3. Red Hat
Hello,
I am in the process of learning Linux OS.
How do I run the below lines of code automatically as root on server startup.
cd /opt/program_folder/ServiceManager/bin
nohup ./servce_manager DEV &
Currently, as soon as the server is up and running I log in as root (as this... (6 Replies)
Discussion started by: rparavastu
6 Replies
4. UNIX Desktop Questions & Answers
Hi,
I'm new to Linux.
I have a windows server that run many processes on it.
In some cases the processes doesn't exit properly or just stop working and the process needs to be killed.
I was wondering how i can automatically (couple of times a day) check which process doesn't use any CPU... (3 Replies)
Discussion started by: ramikom
3 Replies
5. Shell Programming and Scripting
Hi all,
I'm doing automation task for my team and I just started to learn unix scripting so please shed some light on how to do this:
1) I have 2 sets of datafiles - datafile A and B. These datafiles must be loaded subsequently and cannot be loaded concurrently.
2) So I loaded datafile A... (10 Replies)
Discussion started by: luna_soleil
10 Replies
6. AIX
Hello,
I am creating oracle connection from one aix5.2 machine to another aix5.2 database machine. Oracle connection i am reusing it always. If there is now work for java thread to process, oracle instance will be idle and will be active once java thread processes.
We have installed OS... (1 Reply)
Discussion started by: balareddy
1 Replies
7. Shell Programming and Scripting
I am working on a project, which need to constantly watch the process, and check its status, if it was dead, it should be restart automatically.
Please kindly refer me to URL which teach how to write this kind of script, or service.
Thanks. (1 Reply)
Discussion started by: dragondad
1 Replies
8. AIX
Hi,
I am elango. I am working with UNIX AIX version 5.
I am facing tow problem whenever I am trying to run a script.
1. The moment I run the script 3 more jobs are getting started automatically.
I used PS -ef command to check the running Jobs, I found totally 4 jobs
are running for... (4 Replies)
Discussion started by: Elango
4 Replies
9. UNIX for Dummies Questions & Answers
Hi, I need some help, because I'm trying to create a process runing all the time (not invoqued by a crontab), like a daemon, to detect the creation of a new file in a specific directory and axecute a process wich do something with this new file.
Can you help me?
For your information my Unix is... (2 Replies)
Discussion started by: lsquillacioti
2 Replies
SYSTEMD.PATH(5) systemd.path SYSTEMD.PATH(5)
NAME
systemd.path - Path unit configuration
SYNOPSIS
path.path
DESCRIPTION
A unit configuration file whose name ends in ".path" encodes information about a path monitored by systemd, for path-based activation.
This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit
configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The path specific
configuration options are configured in the [Path] section.
For each path file, a matching unit file must exist, describing the unit to activate when the path changes. By default, a service by the
same name as the path (except for the suffix) is activated. Example: a path file foo.path activates a matching service foo.service. The
unit to activate may be controlled by Unit= (see below).
Internally, path units use the inotify(7) API to monitor file systems. Due to that, it suffers by the same limitations as inotify, and for
example cannot be used to monitor files or directories changed by other machines on remote NFS file systems.
If a path unit is beneath another mount point in the file system hierarchy, a dependency between both units is created automatically.
Unless DefaultDependencies=false is used, path units will implicitly have dependencies of type Conflicts= and Before= on shutdown.target.
These ensure that path units are terminated cleanly prior to system shutdown. Only path units involved with early boot or late system
shutdown should disable this option.
OPTIONS
Path files must include a [Path] section, which carries information about the path(s) it monitors. The options specific to the [Path]
section of path units are the following:
PathExists=, PathExistsGlob=, PathChanged=, PathModified=, DirectoryNotEmpty=
Defines paths to monitor for certain changes: PathExists= may be used to watch the mere existence of a file or directory. If the file
specified exists, the configured unit is activated. PathExistsGlob= works similar, but checks for the existence of at least one file
matching the globbing pattern specified. PathChanged= may be used to watch a file or directory and activate the configured unit
whenever it changes. It is not activated on every write to the watched file but it is activated if the file which was open for writing
gets closed. PathModified= is similar, but additionally it is activated also on simple writes to the watched file. DirectoryNotEmpty=
may be used to watch a directory and activate the configured unit whenever it contains at least one file.
The arguments of these directives must be absolute file system paths.
Multiple directives may be combined, of the same and of different types, to watch multiple paths. If the empty string is assigned to
any of these options, the list of paths to watch is reset, and any prior assignments of these options will not have any effect.
If a path already exists (in case of PathExists= and PathExistsGlob=) or a directory already is not empty (in case of
DirectoryNotEmpty=) at the time the path unit is activated, then the configured unit is immediately activated as well. Something
similar does not apply to PathChanged= and PathModified=.
If the path itself or any of the containing directories are not accessible, systemd will watch for permission changes and notice that
conditions are satisfied when permissions allow that.
Unit=
The unit to activate when any of the configured paths changes. The argument is a unit name, whose suffix is not ".path". If not
specified, this value defaults to a service that has the same name as the path unit, except for the suffix. (See above.) It is
recommended that the unit name that is activated and the unit name of the path unit are named identical, except for the suffix.
MakeDirectory=
Takes a boolean argument. If true, the directories to watch are created before watching. This option is ignored for PathExists=
settings. Defaults to false.
DirectoryMode=
If MakeDirectory= is enabled, use the mode specified here to create the directories in question. Takes an access mode in octal
notation. Defaults to 0755.
SEE ALSO
systemd(1), systemctl(8), systemd.unit(5), systemd.service(5), inotify(7), systemd.directives(7)
systemd 208 SYSTEMD.PATH(5)