Pesky here-document warnings

ndom count=200 bs=1 2>/dev/null|LC_ALL=C tr -d -c [:alnum:])`') --- Delimiter END - I have no idea which job could be producing this error? Does it look familiar to anyone? Any ideas on how I can track down the culprit? Regards, -- Mun

Re: Pesky here-document warnings

Linux 5.5 system, and my guess is that the system is running something on my behalf. But I don't know what. At first I was able to ignore the messages because I could not detect any anomalies. But now I've reached my threshold where the messages (sometimes up to about ten in a day) are starting to annoy me. Thanks again for the replies. Regards, -- Mun

Re: Pesky here-document warnings

Hi Greg, On Wed, Nov 17, 2010 at 05:28 AM PST, Greg Wooledge wrote: GW> On Tue, Nov 16, 2010 at 03:13:13PM -0800, Mun wrote: GW> > That's just it, I don't have any cron scripts that use here-documents. GW> GW> at jobs. I don't have any 'at' jobs (that I k

Re: [bash 4.2] In vi mode, cc failed to change the whole line

. Bash no longer deletes the entire line, it just moves the cursor to the first char. I'm using readline v6.2 and bash v4.2 on RHEL5.6 . Regards, -- Mun CJW> I'm using Debian 6.0 (i686) and here's some of my system info: CJW> CJW> # bash --version CJW> GNU bas

Re: [bash 4.2] In vi mode, cc failed to change the whole line

ork fine. CR> CR> Thanks for the report. Please try the attached patch; it fixes the problem CR> in the testing I've done. The patch works perfectly for me. Thanks very much. Regards, -- Mun

Cron jobs, env vars, and group ID ... oh my

! /bin/bash newgrp group1 id -g -n // This shows my login group ID, not group1 export SHELL="/bin/bash -i" /path/setUpEnvVars arg1 arg2 &> /home/mun/out.log <

Re: Cron jobs, env vars, and group ID ... oh my

Hi Greg, Bob, Thanks for your replies. Please see my comments below. On Wed, Nov 28, 2012 at 09:50 AM PST, Greg Wooledge wrote: GW> On Wed, Nov 28, 2012 at 09:10:02AM -0800, Mun wrote: GW> > I need to run a script via cron that in turn launches a script to set up the GW>

Re: Is direxpand available yet (to fix dirspell)?

which release number that is. CR> CR> Bash-4.2.x is bash-4.2 with patches 1-x applied. Where can one find the Bash-4.2.x downloads? I looked on the GNU and cwru.edu web sites and couldn't find them. Thanks and regards, -- Mun

Re: Is direxpand available yet (to fix dirspell)?

at commit. Bash-4.2.41's tarball is CR> http://git.savannah.gnu.org/cgit/bash.git/snapshot/bash-8dea6e878b47519840d57eb215945f3e1fac7421.tar.gz This is exactly what I was looking for; thanks very much. -- Mun

Query regarding ${parameter:-word} usage

27; that tests $# and takes the appropriate branch depending on the number of args (i.e., 0 or non-zero). Any suggestions would be welcomed. Thanks in advance. -- Mun

Re: Query regarding ${parameter:-word} usage

Hi, Thanks for your replies. Please see my comments below. On Wed, Dec 23, 2009 at 05:30 PM PST, Matthew wrote: MW> MW> MW> Mun wrote: MW> > I am moving from ksh93 to bash and have a question regarding the usage MW> > of ${parameter:-word} parameter expansion. MW&g

Re: Query regarding ${parameter:-word} usage

Hi Jan, On Wed, Dec 23, 2009 at 10:52 PM PST, Jan Schampera wrote: JS> JS> JS> Mun schrieb: JS> JS> > nounset on JS> JS> Something sets -u in your startup scripts (or in the script or whatever) That's it! I'm not sure why I had nounset being turned

Sourcing a script renders getopts impotent (or is it just me?)

plish that objective in bash? Regards, -- Mun

Re: Sourcing a script renders getopts impotent (or is it just me?)

27;invoked' is a great idea. Thanks for the quick and very helpful reply! Regards, -- Mun DW> OPTIND=1# also remember to initialize your flags and other variables DW> DW> . . .# do some stuff DW> DW> if some error condition DW> then DW> if [[ $invoked !=

Proper use of nohup within here-document?

e-document I'm essentially calling gxmessage thusly: $ nohup gxmessage -timeout 0 -file abc.txt > /dev/null 2>&1 & Any ideas on how I can allow the here-document to exit but allow the gxmessage process to live on? Thanks, -- Mun