Re: [suse-sparc] syntax error near unexpected token'"(B'

From: Ian Donaldson (ian@dsd-tech.co.uk)
Date: Tue Jun 12 2001 - 15:05:37 PDT

  • Next message: Kirk Moore @ Moore Webs: "[suse-sparc] SS20 with 2.25 bois..." 

    From: Ian Donaldson <ian@dsd-tech.co.uk>
Date: Tue, 12 Jun 2001 23:05:37 +0100
Message-Id: <01061223101600.00720@sparc>
Subject: Re: [suse-sparc] syntax error near unexpected token'"(B'

    On Tue, 12 Jun 2001, Lou Picciano / Essex Systems wrote:
    >
    > All:
    >
    > After a recent edit of my rc.config file, I have started getting the
    > message:
    >
    > syntax error near unexpected token'"(B' #CONSOLE_MAGIC can be empty
    > or have..." etc.
    >
    > I have been using Text Editor to edit my configureation files, and have been
    > careful to keep word wrapping off, so as not to introduce any carriage
    > returns or newlines. Please note also that I have edited the file nowhere
    > _near_ the CONSOLE_MAGIC area.
    >
    > I can only guess that something in the SuSEconfig run is introducing some
    > bizarre character, causing the interpreter to ignore my leading '#'
    > characters around this part of the rc.config file. This has the added
    > annoyance of filling my monitor, at startup, with pages of the above error
    > as my rc.config file is processed. My evidence that it might be SuSEconfig
    > is that this exact behavior has happened before, and always when I have not
    > been near the CONSOLE_MAGIC variable!
    >
    > Even if I knew which script was the 'offender', I'm not sure I'd know how to
    > fix it!
    >
    > Does anyone know a resolution to this?
    >
    > At the very least, how can I 'vacuum' my rc.config to find the offending
    > characters??
    >
    > TIA, Lou
    >

    ----------------------------------------
    Content-Type: text/html; name="unnamed"
    Content-Transfer-Encoding: quoted-printable
    Content-Description:
    ----------------------------------------

    I had the same problem happen to me in the apache config file, and yes dispit
    your efforts it is word wrapping that is to blame. I eventually sorted it out,
    but ever since then I always copy any config file to ???????.working before
    starting to edit, at least that way you alway have a working copy. 

    -- 
			 Regards      Ian Donaldson

    Newtownards					
Northern Ireland			       
ian@dsd-tech.co.uk			      	
ian@ards.freeserve.co.uk

    -- 
To unsubscribe, e-mail: suse-sparc-unsubscribe@suse.com
For additional commands, e-mail: suse-sparc-help@suse.com

    This archive was generated by hypermail 2.1.0 : Tue Jun 12 2001 - 15:08:51 PDT