I use the --quiet option but then the output changes from tracing patch 1 tracing patch 2
etc... to tracing patch 1 and then only flipping this number and not rewriting the line. So it does not respect the --quiet option completely... And the 2> /dev/null option seems to work, now my script can run in the background and I can keep working. Thanks, Koen -----Original Message----- From: Paul Kelly [mailto:[email protected]] Sent: Mon 29-12-2008 17:36 To: Hufkens Koen Cc: [email protected] Subject: Re: [GRASS-user] suppress output to terminal completely On Mon, 29 Dec 2008, Hufkens Koen wrote: > > Hi list, > > I'm working with r.le.patch in both scripts as well as interactively on the > terminal. > > Since these calculations take up a lot of time I would like to move them to > the background. > > If I use r.le.patch -mysettings & this will do just that. > > However, the module still spews stuff to my terminal. This is very annoying > as I login remotely so I can't fall back on the GUI menus. > > Can I disable my terminal output completely? > > dumping stout to /dev/null does not seem to work... GRASS modules send informative messages to stderr, not stdout - so adding 2>/dev/null (Bash shell syntax) should work. But have you tried r.le.patch --quiet first of all? I'm not sure if r.le.patch respects the --quiet setting, but redirecting stderr to /dev/null definitely will work. Paul
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
