Linuxconf fails to handle chat scripts containing # in
response strings. Comments in chat scripts are marked by a #
in the first position of a line. It is valid to include a #
inside strings. Linuxconf seems to consider a # as a comment
marker regardless of its context. It also removes
significant trailing whitespace at the end of strings, even
when enclosed in single quotes (').
The problem is manifest in the configuration of PPP devices.
Could you send us a sample chat-ppp0 script where this is failing for
you (minus user account info). Thanks.
Added Jacques to CC list
Requested chat script example with the corresponding damaged version
produced by linuxconf were sent to firstname.lastname@example.org on 12-APR-1999.
This issue has been forwarded to a developer for further action.
Jacques, have you had a chance to look into this yet?
Jacques, can you look at this, please?
*** Bug 2668 has been marked as a duplicate of this bug. ***
A PAP password entered with gnome-linuxconf that contains an
octothorpe '#' character appears to cause pppd to truncate
the password, causing logins to fail. '#' (and maybe other
characters) must be backslash quoted in the
------- Additional Comments From email@example.com 08/27/99 19:07 -------
*** Bug 4753 has been marked as a duplicate of this bug. ***
I am setting up a system that uses PPP to dial out to a
server. To dial out through the PBX at that location, you
must dial a "#" first. This character is a comment
character to the "chat" program if it is at the beginning of
a line, but not anywhere else on the line. However,
linuxconf cannot handle the "#" in the dial string. If I
put it in and save the interface and then go back in to the
interface configuration screen, the dial number is empty
(like linuxconf sees "#" as a comment anywhere and tosses
it). It looks like linuxconf does not even save the dial
number; if I go in and manually edit
/etc/sysconfig/network-scripts/chat-ppp0, it just has a line
and I have to manually put in the number to dial. If I go
back in to linuxconf and do anything to the interface I have
to again manually put the number in.
*** Bug 7715 has been marked as a duplicate of this bug. ***
Jacques' partial fix (# taken literally) is in linuxconf-1.10r16-3,
which will be in the next RawHide release. That does not address
the literal whitespace problem.
Oops, make that linuxconf-1.16r10-3, sorry for the version typo.
As of linuxconf 1.17r7, all chat strings are single-quoted by default, but a
single quote within a string needs to be manually escaped. This will be fixed in
linuxconf-1.17r7-2 in Raw Hide.