Lukas Ocilka wrote:
The Nice Spider wrote:
----- Original Message ----- From: "Volker Kuhlmann" <hidden@paradise.net.nz> ...
In your example, you could write
FW_SERVICES_EXT_TCP=" 80 443 21 "
or
FW_SERVICES_EXT_TCP= FW_SERVICES_EXT_TCP="$FW_SERVICES_EXT_TCP 80" FW_SERVICES_EXT_TCP="$FW_SERVICES_EXT_TCP 443" FW_SERVICES_EXT_TCP="$FW_SERVICES_EXT_TCP 21"
if you wanted to. Don't necessarily expect yast to still be able to handle it then though.
Volker
oo... thanks for the last tip, that's what i really needed!
On the other hand, if you experience such problem, you might try to file a bugreport to bugzilla. Despite the fact that YaST maybe isn't able to be able to handle this multiline configuration, it necessarily needn't stay that way ;)
Almost everything can be enhanced if it makes sense to do it (that means: it isn't too expensive and it's relatively easy to implement it).
By the way, too late to file a bugreport :) New entry in yast2.changes - Fixed handling of multiline entries in the SuSEfirewall2 sysconfig file. Newline characters were removed when joining multiline entries together. By now, .sysconfig.SuSEfirewall2 returns values as it reads them, newlines are replaced with spaces in SuSEFirewall::Read() (#194419). This should appear in yast2-2.13.69 Lukas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org