Bug 103013

Summary:	Output from ag_initscripts can be broken when comment in init script contains backslash
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Lukas Ocilka <locilka>
Component:	YaST2	Assignee:	Martin Vidner <mvidner>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 1
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Lukas Ocilka 2005-08-09 12:55:17 UTC

see: Description in /etc/init.d/subdomain
Package: subdomain-parser-common-1.2-19_imnx_suse

# Description: SubDomain rc file. This rc script inserts the subdomain \
#              module and runs the parser on the /etc/subdomain.d/ \
#              directory.

Affected module: yast2-runlevel
Affected usage:  `Read (.init.scripts.comments)

Comment 1 Lukas Ocilka 2005-08-09 12:55:52 UTC

BTW: thanks again for the debug ;)

Comment 2 Martin Vidner 2005-08-09 14:12:57 UTC

Even trickier, the bug occurs only if the backslash is followed by a line that 
terminates the description, in this case the second line has #<SPC><TAB> which 
triggers another funny buglet in the parser. 
 
In such case `Read (.init.scripts.comments) returns nil and y2log reports a 
parse error in ag_initscripts:42 where 42 is a line number in the output of 
"echo '`Read (.comments)' | /usr/lib/YaST2/servers_non_y2/ag_initscripts" 
 
Fixed in SVN.

Comment 3 Martin Vidner 2005-10-21 12:13:32 UTC

Now we have this problem in SLES9 SP3 too

Comment 4 Martin Vidner 2005-10-21 14:33:33 UTC

fixed in yast2-2.9.89