With fresh 9.1 install, bash completion no longer expands $HOME

2013-06-10 Thread David P. Caldwell
On my 9.0-based machines, if I typed $HOME[tab] when typing a command in bash, the $HOME would be overwritten by the actual path to my home directory (the value of $HOME) and tab completion would work as expected. After a fresh 9.1 install, this does not work as well. $HOME is still detected by

Coredumps settings for user programm

2013-06-10 Thread Vagner
Hello! Tell me please, can i setting coredumps write mechanism for write only stack of programm and current frame? -- Respectfully, Stanislav Putrya System administrator FotoStrana.Ru Ltd. ICQ IM: 328585847 Jabber-GoogleTalk: root.vagner mob.phone SPB: +79215788755 mob.phone RND: +79525600664

Re: With fresh 9.1 install, bash completion no longer expands $HOME

2013-06-10 Thread Jeremy Chadwick
Re: http://lists.freebsd.org/pipermail/freebsd-questions/2013-June/251607.html This has nothing to do with FreeBSD 9.0 vs. 9.1 other than the fact that the package on 9.0 is older than 9.1. Instead, this has everything to do with the difference between bash versions you're using. Remember:

[SOLVED] Re: www/179397: I used mouse focus in open-motif and shift-click3 to iconify xterms, doing so causes cursor to disappear and mouse is unusable!

2013-06-10 Thread William Bulley
According to freebsd-gnats-sub...@freebsd.org on Fri, 06/07/13 at 06:40: Thank you very much for your problem report. It has the internal identification `www/179397'. The individual assigned to look at your report is: freebsd-www. You can access the state of your problem report at any time

Suddenly Seeing Clamav Errors After MailScanner Update

2013-06-10 Thread Tim Daneliuk
I am working on a FBSD 9.1-STABLE mail machine that's been working fine. After upgrading to MailScanner 4.84.5_3, we are now suddenly seeing like this: Clamd::ERROR:: UNKNOWN CLAMD RETURN ./lstat() failed: Permission denied. ERROR :: /var/spool/MailScanner/incoming/68340 Any ideas what

Re: buildworld selectively?

2013-06-10 Thread Walter Hurry
On Sun, 09 Jun 2013 21:08:23 -0400, Robert Huff wrote: Walter Hurry writes: Fair enough. Point taken, thanks. Nevertheless I see no reason to compile stuff I neither want nor need. While I endorse the principle ... it can be difficult for the casual user to know which parts can

Bourne shell if syntax

2013-06-10 Thread lconrad
script fragment: PTR=`dig @some.dns +short +norec -x a.b.c.d` echo $PTR if [ $PTR ==] ; then echo $PTR /path/to/PTR_absent.txt fi === output for an IP: a-b-c-d.domain.net. [: a-b-c-d.domain.net.: unexpected operator thanks Len

RE: Bourne shell if syntax

2013-06-10 Thread dteske
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of lcon...@go2france.com Sent: Monday, June 10, 2013 11:53 AM To: freebsd-questions@freebsd.org Subject: Bourne shell if syntax script fragment: PTR=`dig

RE: Bourne shell if syntax

2013-06-10 Thread dteske
-Original Message- From: Devin Teske [mailto:devin.te...@fisglobal.com] On Behalf Of dte...@freebsd.org Sent: Monday, June 10, 2013 11:59 AM To: lcon...@go2france.com; freebsd-questions@freebsd.org Cc: Devin Teske Subject: RE: Bourne shell if syntax -Original

Re: Bourne shell if syntax

2013-06-10 Thread Tim Daneliuk
On 06/10/2013 01:53 PM, lcon...@go2france.com wrote: script fragment: PTR=`dig @some.dns +short +norec -x a.b.c.d` echo $PTR if [ $PTR ==] ; then echo $PTR /path/to/PTR_absent.txt fi === output for an IP: a-b-c-d.domain.net. [: a-b-c-d.domain.net.: unexpected

Re: Bourne shell if syntax

2013-06-10 Thread Tim Daneliuk
On 06/10/2013 01:59 PM, dte...@freebsd.org wrote: -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of lcon...@go2france.com Sent: Monday, June 10, 2013 11:53 AM To: freebsd-questions@freebsd.org Subject: Bourne shell

Re: Bourne shell if syntax

2013-06-10 Thread Mark Felder
On Mon, 10 Jun 2013 14:05:45 -0500, Tim Daneliuk tun...@tundraware.com wrote: if [ _$PTR == _ ] ; then I've never seen this syntax before. Intriguing! ___ freebsd-questions@freebsd.org mailing list

RE: Bourne shell if syntax

2013-06-10 Thread dteske
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Tim Daneliuk Sent: Monday, June 10, 2013 12:06 PM To: freebsd-questions@freebsd.org Subject: Re: Bourne shell if syntax On 06/10/2013 01:59 PM,

Re: Bourne shell if syntax

2013-06-10 Thread Tim Daneliuk
On 06/10/2013 02:10 PM, dte...@freebsd.org wrote: -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Tim Daneliuk Sent: Monday, June 10, 2013 12:06 PM To: freebsd-questions@freebsd.org Subject: Re: Bourne shell if

RE: Bourne shell if syntax

2013-06-10 Thread dteske
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Tim Daneliuk Sent: Monday, June 10, 2013 12:17 PM To: dte...@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Re: Bourne shell if syntax On 06/10/2013

Re: Bourne shell if syntax

2013-06-10 Thread Michael Sierchio
On Mon, Jun 10, 2013 at 12:16 PM, Tim Daneliuk tun...@tundraware.com wrote: That wasn't really my point. I use sentinels because in the face of an empty string this: if [ $PTR = ] Actually evaluates to: if [ = ] Which throws an error. Right. Many scripts seem to assume that

RE: Bourne shell if syntax

2013-06-10 Thread dteske
-Original Message- From: Devin Teske [mailto:devin.te...@fisglobal.com] On Behalf Of dte...@freebsd.org Sent: Monday, June 10, 2013 12:19 PM To: tun...@tundraware.com; freebsd-questions@freebsd.org Cc: dte...@freebsd.org Subject: RE: Bourne shell if syntax -Original

Re: Bourne shell if syntax

2013-06-10 Thread Tim Daneliuk
On 06/10/2013 02:21 PM, dte...@freebsd.org wrote: ctually, there's another reason you should also avoid the above (unquoted parameter), and that's in the case of a multi-word value. For example: Yup, that's the compelling case for using quoting. --

Re: Bourne shell if syntax

2013-06-10 Thread jb
Michael Sierchio kudzu at tenebras.com writes: ... Right. Many scripts seem to assume that sh is bash, and that's certainly not the case here. if [ x$BLAH = x ]; then is the most reliable and portable way of determining if it's a string of zero length. Actually this trick is not

Re: buildworld selectively?

2013-06-10 Thread Adam Vande More
On Sun, Jun 9, 2013 at 4:27 PM, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: Walter Hurry walterhu...@gmail.com writes: Ah, src.conf. That's what I missed!. Thank you so much Gary, and sorry if it was a silly question. Bear in mind that you're only going to be able to

Your Ticket Order Confirmation

2013-06-10 Thread Ticket Master
Thank you for purchasing tickets on Ticketmaster.Your order number for this purchase is 18-00609/AUS.Complete order detail is attached to this e-mail.You will receive your tickets via: International Express-Ticketmaster will mail these within 2 business days of the booking.Tickets usually

Your Ticket Order Confirmation

2013-06-10 Thread Ticket Master
Thank you for purchasing tickets on Ticketmaster.Your order number for this purchase is 06-89624/AUS.Complete order detail is attached to this e-mail.You will receive your tickets via: International Express-Ticketmaster will mail these within 2 business days of the booking.Tickets usually

Re: buildworld selectively?

2013-06-10 Thread Robert Huff
Walter Hurry writes: Fair enough. Point taken, thanks. Nevertheless I see no reason to compile stuff I neither want nor need. While I endorse the principle ... it can be difficult for the casual user to know which parts can be removed without blowing up things they want.

RE: Bourne shell if syntax

2013-06-10 Thread dteske
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of jb Sent: Monday, June 10, 2013 12:53 PM To: freebsd-questions@freebsd.org Subject: Re: Bourne shell if syntax Michael Sierchio kudzu at tenebras.com writes:

Re: Suddenly Seeing Clamav Errors After MailScanner Update

2013-06-10 Thread Sean DuBois
Hi Tim, Double check what user clamd is run as, and what permissions your mail spool have. Somewhere along the line your mail spool locked out clamd The lstat system call's man page says `execute (search) permission is required on all of the directories in path that lead to the file.` Also,