Sponsored Content
Top Forums UNIX for Advanced & Expert Users Email notifications when new directory is created. Post 303023102 by jim mcnamara on Wednesday 12th of September 2018 12:33:51 AM
Old 09-12-2018
Linux has inotifywait. Read about it. It will tell you anytime a directory (or whatever type of file you ask for) is created, deleted, etc. You need to run it with privilege.

Please provide full details of your problem for more help.
 

9 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

trying to turn email notifications off

I'm trying to disable the email notifications; despite going into my control panel and selecting NO next to Use 'Email Notification' by default? I keep getting email notifications anyway! And I know I've never selected the checkbox next to Email Notification: emails sent to you whenever someone... (2 Replies)
Discussion started by: oombera
2 Replies

2. Shell Programming and Scripting

how to prevent multiple email notifications from monitoring script

Hi everyone, I am in the process of trying to decide the correct way to solve a particular scripting/email issue I have and would appreciate any advice. We have a cronjob running every 10 mins to check disk size on the server and if this exceeds a certain percentage then it will email a... (2 Replies)
Discussion started by: si_linux
2 Replies

3. Post Here to Contact Site Administrators and Moderators

Servers, email notifications

Hi. On 09-05-2007 Neo posted that new servers were on their way. 1) It would be nice to hear of occasional progress. As far as I can tell, there has not been much of a change. The notice that is posted every now and then talks about a new server "this week". (In fact as I was previewing... (1 Reply)
Discussion started by: drl
1 Replies

4. AIX

Crontab - Email notifications by alternate user

Hi, I have a crontab which sents email to a group in a certain interval. The email contains my user id in 'from' field of email - because my user crontab. I don't have root access for that AIX 5.3 host - and should have to change 'from' field to either 'root' or any other common names. ... (4 Replies)
Discussion started by: vasukv
4 Replies

5. Solaris

OPS Center Email Notifications

Hi, Does any one know how to configure email notifications (to exchange) in Oracle Enterprise Manager 11g OPS Center? I have gone through the documentation and have done everything it asked, but still no notifications via email. I get the following error: At the OS level i tried sending email... (20 Replies)
Discussion started by: Mack1982
20 Replies

6. Windows & DOS: Issues & Discussions

Fail2ban: email notifications and banning ssh IP logins

Hi all. I am using Cygwin in Windows 7 and am trying to setup fail2ban so that I can ban foreign IP addresses under SSH, also getting email notifications. I downloaded fail2ban and installed it. I then created jail.local copy from jail.conf and changed some values in jail.local. Now when I try to... (2 Replies)
Discussion started by: synthesis
2 Replies

7. Shell Programming and Scripting

Email Notifications on Cron Bash Error Only cp mv rsync

Wondering if anyone can point me to an example of how to setup a bash script that executes cp mv and rsync commands and only sends an email if there were errors with any of those commands and what the errors are. In addition it should email if the cron event to execute the script fails, or in... (1 Reply)
Discussion started by: consultant
1 Replies

8. HP-UX

Email notifications of PAX backups

I have just switched my production server from using the br_backup script that uses fbackup to the fs_backup script that uses PAX. Things seem to work fine and test restores are successful, but I'm not getting a daily e-mail with the backup results that I used to get from the br_backup script. ... (2 Replies)
Discussion started by: jduehmig
2 Replies

9. Shell Programming and Scripting

Check the new directory and send notifications

Hi Team, I am completely new to Unix programming. I need your help regarding below requirements. I am working on bash shell I have a directory called /home/vvv Whenever new directory is created under /home/vvv then notify mail shd be triggered. Thanks in advance. (0 Replies)
Discussion started by: Dhivyaprabha
0 Replies
inotifywait(1)						      General Commands Manual						    inotifywait(1)

NAME
inotifywait - wait for changes to files using inotify SYNOPSIS
inotifywait [-hcmrq] [-e <event> ] [-t <seconds> ] [--format <fmt> ] [--timefmt <fmt> ] <file> [ ... ] DESCRIPTION
inotifywait efficiently waits for changes to files using Linux's inotify(7) interface. It is suitable for waiting for changes to files from shell scripts. It can either exit once an event occurs, or continually execute and output events as they occur. OUTPUT
inotifywait will output diagnostic information on standard error and event information on standard output. The event output can be config- ured, but by default it consists of lines of the following form: watched_filename EVENT_NAMES event_filename watched_filename is the name of the file on which the event occurred. If the file is a directory, a trailing slash is output. EVENT_NAMES are the names of the inotify events which occurred, separated by commas. event_filename is output only when the event occurred on a directory, and in this case the name of the file within the directory which caused this event is output. By default, any special characters in filenames are not escaped in any way. This can make the output of inotifywait difficult to parse in awk scripts or similar. The --csv and --format options will be helpful in this case. OPTIONS
-h, --help Output some helpful usage information. @<file> When watching a directory tree recursively, exclude the specified file from being watched. The file must be specified with a rela- tive or absolute path according to whether a relative or absolute path is given for watched directories. If a specific path is explicitly both included and excluded, it will always be watched. Note: If you need to watch a directory or file whose name starts with @, give the absolute path. --fromfile <file> Read filenames to watch or exclude from a file, one filename per line. If filenames begin with @ they are excluded as described above. If <file> is `-', filenames are read from standard input. Use this option if you need to watch too many files to pass in as command line arguments. -m, --monitor Instead of exiting after receiving a single event, execute indefinitely. The default behaviour is to exit after the first event occurs. -d, --daemon Same as --monitor, except run in the background logging events to a file that must be specified by --outfile. Implies --syslog. -o, --outfile <file> Output events to <file> rather than stdout. -s, --syslog Output errors to syslog(3) system log module rather than stderr. -r, --recursive Watch all subdirectories of any directories passed as arguments. Watches will be set up recursively to an unlimited depth. Sym- bolic links are not traversed. Newly created subdirectories will also be watched. Warning: If you use this option while watching the root directory of a large tree, it may take quite a while until all inotify watches are established, and events will not be received in this time. Also, since one inotify watch will be established per subdi- rectory, it is possible that the maximum amount of inotify watches per user will be reached. The default maximum is 8192; it can be increased by writing to /proc/sys/fs/inotify/max_user_watches. -q, --quiet If specified once, the program will be less verbose. Specifically, it will not state when it has completed establishing all inotify watches. If specified twice, the program will output nothing at all, except in the case of fatal errors. --exclude <pattern> Do not process any events whose filename matches the specified POSIX extended regular expression, case sensitive. --excludei <pattern> Do not process any events whose filename matches the specified POSIX extended regular expression, case insensitive. -t <seconds>, --timeout <seconds> Exit if an appropriate event has not occurred within <seconds> seconds. If <seconds> is a negative value (the default), wait indefi- nitely for an event. -e <event>, --event <event> Listen for specific event(s) only. The events which can be listened for are listed in the EVENTS section. This option can be spec- ified more than once. If omitted, all events are listened for. -c, --csv Output in CSV (comma-separated values) format. This is useful when filenames may contain spaces, since in this case it is not safe to simply split the output at each space character. --timefmt <fmt> Set a time format string as accepted by strftime(3) for use with the `%T' conversion in the --format option. --format <fmt> Output in a user-specified format, using printf-like syntax. The event strings output are limited to around 4000 characters and will be truncated to this length. The following conversions are supported: %w This will be replaced with the name of the Watched file on which an event occurred. %f When an event occurs within a directory, this will be replaced with the name of the File which caused the event to occur. Other- wise, this will be replaced with an empty string. %e Replaced with the Event(s) which occurred, comma-separated. %Xe Replaced with the Event(s) which occurred, separated by whichever character is in the place of `X'. %T Replaced with the current Time in the format specified by the --timefmt option, which should be a format string suitable for passing to strftime(3). EXIT STATUS
0 The program executed successfully, and an event occurred which was being listened for. 1 An error occurred in execution of the program, or an event occurred which was not being listened for. The latter generally occurs if something happens which forcibly removes the inotify watch, such as a watched file being deleted or the filesystem containing a watched file being unmounted. 2 The -t option was used and an event did not occur in the specified interval of time. EVENTS
The following events are valid for use with the -e option: access A watched file or a file within a watched directory was read from. modify A watched file or a file within a watched directory was written to. attrib The metadata of a watched file or a file within a watched directory was modified. This includes timestamps, file permissions, extended attributes etc. close_write A watched file or a file within a watched directory was closed, after being opened in writeable mode. This does not necessarily imply the file was written to. close_nowrite A watched file or a file within a watched directory was closed, after being opened in read-only mode. close A watched file or a file within a watched directory was closed, regardless of how it was opened. Note that this is actually imple- mented simply by listening for both close_write and close_nowrite, hence all close events received will be output as one of these, not CLOSE. open A watched file or a file within a watched directory was opened. moved_to A file or directory was moved into a watched directory. This event occurs even if the file is simply moved from and to the same directory. moved_from A file or directory was moved from a watched directory. This event occurs even if the file is simply moved from and to the same directory. move A file or directory was moved from or to a watched directory. Note that this is actually implemented simply by listening for both moved_to and moved_from, hence all close events received will be output as one or both of these, not MOVE. move_self A watched file or directory was moved. After this event, the file or directory is no longer being watched. create A file or directory was created within a watched directory. delete A file or directory within a watched directory was deleted. delete_self A watched file or directory was deleted. After this event the file or directory is no longer being watched. Note that this event can occur even if it is not explicitly being listened for. unmount The filesystem on which a watched file or directory resides was unmounted. After this event the file or directory is no longer being watched. Note that this event can occur even if it is not explicitly being listened to. EXAMPLES
Example 1 Running inotifywait at the command-line to wait for any file in the `test' directory to be accessed. After running inotifywait, `cat test/foo' is run in a separate console. % inotifywait test Setting up watches. Watches established. test/ ACCESS foo Example 2 A short shell script to efficiently wait for httpd-related log messages and do something appropriate. #!/bin/sh while inotifywait -e modify /var/log/messages; do if tail -n1 /var/log/messages | grep httpd; then kdialog --msgbox "Apache needs love!" fi done Example 3 A custom output format is used to watch `~/test'. Meanwhile, someone runs `touch ~/test/badfile; touch ~/test/goodfile; rm ~/test/badfile' in another console. % inotifywait -m -r --format '%:e %f' ~/test Setting up watches. Beware: since -r was given, this may take a while! Watches established. CREATE badfile OPEN badfile ATTRIB badfile CLOSE_WRITE:CLOSE badfile CREATE goodfile OPEN goodfile ATTRIB goodfile CLOSE_WRITE:CLOSE goodfile DELETE badfile BUGS
There are race conditions in the recursive directory watching code which can cause events to be missed if they occur in a directory immedi- ately after that directory is created. This is probably not fixable. It is assumed the inotify event queue will never overflow. AUTHORS
inotifywait is written and maintained by Rohan McGovern <rohan@mcgovern.id.au>. inotifywait is part of inotify-tools. The inotify-tools website is located at: http://inotify-tools.sourceforge.net/ SEE ALSO
inotifywatch(1), strftime(3), inotify(7) inotifywait 3.20.1 August 05, 2019 inotifywait(1)
All times are GMT -4. The time now is 04:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy