18 Jul
2005
18 Jul
'05
07:16
Bernd Johannes wrote:
maybe I got this malfunction by chance but I will report it anyway - perhaps someone else got hit.
During a recent update of my Suse9.2 (within the last 3-4 weeks) my sysconfig/SuSEfirewall2 config file got modified in a bad way. The cause was a multiline configuration entry with "" to span to the next line(s).
Don't do that :-) Although sysconfig files can be sourced by bash they are no shell scripts but config files. Only name=value is allowed. Any sysconfig file will break during update if you use shell tricks. cu Ludwig -- (o_ Ludwig Nussel //\ SUSE LINUX Products GmbH, Development V_/_ http://www.suse.de/