Re: nother bash question

On Monday 13 June 2016 13:53:14 Thomas Schmitt wrote: > Hi, > > > ++ /usr/bin/inotifywait -q -e close --format %f /var/spool/mail/ > > From the man page i learn that you let it watch the whole directory. > This way you get notifications about any file in there. > > The empty variable content possi

Re: nother bash question

On Monday 13 June 2016 10:08:33 David Wright wrote: > On Mon 13 Jun 2016 at 10:19:46 (+0200), Thomas Schmitt wrote: > > Gene Heskett wrote: > > > if test ${InMail} = "gene" > > > bin/mailwatcher: line 66: test: =: unary operator expected > > > > The syntax problem is most probably about missing "-

Re: nother bash question

On Monday 13 June 2016 08:50:58 Jörg-Volker Peetz wrote: > watch -d -n 1.5  ls -la /var/spool/mail/ Interesting tool, thank you. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Ge

Re: nother bash question

Hi, > ++ /usr/bin/inotifywait -q -e close --format %f /var/spool/mail/ >From the man page i learn that you let it watch the whole directory. This way you get notifications about any file in there. The empty variable content possibly stems from this feature: "-format ... %f When an ev

Re: nother bash question

On Monday 13 June 2016 06:34:00 Gene Heskett wrote: > On Monday 13 June 2016 05:21:23 to...@tuxteam.de wrote: > > On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote: > > > Hi, > > > > > > Gene Heskett wrote: > > > > if test ${InMail} = "gene" > > > > bin/mailwatcher: line 66: test: =:

Re: nother bash question

On Monday 13 June 2016 06:30:39 Thomas Schmitt wrote: > Hi, > > i wrote: > > > Is ${InMail} supposed to be empty ? It is not supposed to be. Empty only if I kill it with a killall in practice. > > Gene Heskett wrote: > > That is set by inotifywait's return of the name of the file that > > procma

Re: nother bash question

Hi, David Wright wrote: > Thomas, your patience appears unbounded. That's a character strength which a programmer must have at least in part. > https://lists.debian.org/debian-user/2016/04/msg00652.html Yeah. I advised Gene to put "-quotes around variable evaluations. Now we have the education

Re: nother bash question

On Monday 13 June 2016 05:21:23 to...@tuxteam.de wrote: > On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote: > > Hi, > > > > Gene Heskett wrote: > > > if test ${InMail} = "gene" > > > bin/mailwatcher: line 66: test: =: unary operator expected > > > > The syntax problem is most probabl

Re: nother bash question

On Mon 13 Jun 2016 at 05:17:42 (-0400), Gene Heskett wrote: > On Monday 13 June 2016 04:19:46 Thomas Schmitt wrote: > > > Hi, > > > > Gene Heskett wrote: > > > if test ${InMail} = "gene" > > > bin/mailwatcher: line 66: test: =: unary operator expected > > > > The syntax problem is most probably ab

Re: nother bash question

On Mon 13 Jun 2016 at 10:19:46 (+0200), Thomas Schmitt wrote: > Gene Heskett wrote: > > if test ${InMail} = "gene" > > bin/mailwatcher: line 66: test: =: unary operator expected > > The syntax problem is most probably about missing "-quotes around > the variable ecaluation ${InMail} which would ha

Re: nother bash question

Gene Heskett wrote on 06/13/16 12:34: > In any event a pair of "" around the left argument silenced the warning, > and it still works. However it may be that inotifywait is premature, as > I see that InMail occasionall contains a hash name of the order of: > + test _KQG,TdoXXB.coyote = gene > +

Re: nother bash question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jun 13, 2016 at 12:30:39PM +0200, Thomas Schmitt wrote: > Hi, [...] > to...@tuxteam.de wrote: > > One could argue "unary operator expected" is a strange way to > > restate this. > > It's the way how the gild of land surveyors and bean counte

Re: nother bash question

On Monday 13 June 2016 05:21:23 to...@tuxteam.de wrote: > On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote: > > Hi, > > > > Gene Heskett wrote: > > > if test ${InMail} = "gene" > > > bin/mailwatcher: line 66: test: =: unary operator expected > > > > The syntax problem is most probabl

Re: nother bash question

Hi, i wrote: > > Is ${InMail} supposed to be empty ? Gene Heskett wrote: > That is set by inotifywait's return of the name of the file that procmail > just closed. Hmm. I don't have inotifywait installed. According to http://linux.die.net/man/1/inotifywait it should put out lines like CLOSE_

Re: nother bash question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jun 13, 2016 at 10:19:46AM +0200, Thomas Schmitt wrote: > Hi, > > Gene Heskett wrote: > > if test ${InMail} = "gene" > > bin/mailwatcher: line 66: test: =: unary operator expected > > The syntax problem is most probably about missing "-quotes

Re: nother bash question

On Monday 13 June 2016 04:19:46 Thomas Schmitt wrote: > Hi, > > Gene Heskett wrote: > > if test ${InMail} = "gene" > > bin/mailwatcher: line 66: test: =: unary operator expected > > The syntax problem is most probably about missing "-quotes around > the variable ecaluation ${InMail} which would ha

Re: nother bash question

Hi, Gene Heskett wrote: > if test ${InMail} = "gene" > bin/mailwatcher: line 66: test: =: unary operator expected The syntax problem is most probably about missing "-quotes around the variable ecaluation ${InMail} which would have to be empty to cause the message: $ test $notdefined = "hello w

nother bash question

Greetings bashers; I have a set -x at the top of this script, and this line, while working as expected: if test ${InMail} = "gene" also spits out this warning: bin/mailwatcher: line 66: test: =: unary operator expected What syntax correction does this need? Thanks. Cheers, Gene Heskett -- "