public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] pop up windows with text message
Date: Thu, 11 Jul 2013 09:28:57 +0100	[thread overview]
Message-ID: <20130711092857.3474e361@hactar.digimed.co.uk> (raw)
In-Reply-To: <20130711024822.GB17831@syscon7.inet>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

On Wed, 10 Jul 2013 20:48:22 -0600, Joseph wrote:

> Thanks Alan, yes I'm looking into it and your are the second person who
> suggested to me "inotify" is the tool for the job. I've installed
> inotify-tools but I think I will need to find more samples to make it
> to work :-)

Try incron, it uses the kernel's inotify functions but does the work
for you, and it comes with plenty of examples.

> Once I copy the file, the system should notify a use that new file
> exist (a message pop-up).  If the use closes the message and will not
> open the file, after few ours I want to remind the user that the file
> has not been open yet. 

incron could launch one script you when the file is created. This
would send the notification and create an at job to send another
notification after a specified time. Then you could have another
icrond task triggered by the file being opened for read, that kills
the at job


-- 
Neil Bothwick

God is real, unless specifically declared integer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-07-11  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 16:54 [gentoo-user] pop up windows with text message Joseph
2013-07-09 22:52 ` Neil Bothwick
2013-07-10  9:21 ` Alan McKinnon
2013-07-11  2:48   ` Joseph
2013-07-11  4:47     ` Wang Xuerui
2013-07-11  8:28     ` Neil Bothwick [this message]
2013-07-13  3:06       ` Joseph
2013-07-11  5:12 ` Mark David Dumlao
2013-07-13 22:59 ` felix
2013-07-15 18:17   ` Joseph

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130711092857.3474e361@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox