Re: FVWM: issues with noclobber shell variable

From: Dominik Vogt <dominik.vogt_at_gmx.de>
Date: Tue, 15 Jun 1999 11:36:34 -0600

On Mon, Jun 14, 1999 at 12:39:29PM -0700, martink_at_physics.ubc.ca wrote:
>
> Cheers all!
>
> I have found that I cannot start fvwm if my noclobber variable is set. It
> appears that fvwm95 cannot clobber (overwrite) a file /tmp/fvwmrcaxxxxx
> that it creates and therefore cannot start. This file is created after
> fvwm is executed, because deleting any fvwmrc files in /tmp before execing
> fvwm does not solve the problem.

Note that this is the wrong place to ask questions about fvwm95. It's
a spin off of fvwm2 and is not maintained on this list. I don't think
fvwm95 is actively maintained at all.

> The error message appears in .FVWM2-errors and it's something like
>
> sh: FVWM cannot clobber file /tmp/fvwmrcaxxxxxx
>
> Question is, how do I have noclobber on and bypass this problem?

Try to explicitly remove the old file. If you start fvwm95 from
.xinitrc you could try to insert this line before the line that
starts the WM:

  rm /tmp/fvwmrca*

Of course you should only delete your own files :)

Bye

Dominik ^_^

-- 
Dominik Vogt, Hewlett-Packard GmbH, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/14-4596, fax: 07031/14-3883, dominik_vogt_at_hp.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Jun 15 1999 - 04:37:22 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:02 BST