Bug 103013 - Output from ag_initscripts can be broken when comment in init script contains backslash
Summary: Output from ag_initscripts can be broken when comment in init script contains...
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 1
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Martin Vidner
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-09 12:55 UTC by Lukas Ocilka
Modified: 2005-10-21 14:33 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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