SuSEconfig information?
Hi. On my SuSE 10.1 I have manually changed the /etc/postfix/master.cf. When I after ran SuSEconfig, I got this: Executing /sbin/conf.d/SuSEconfig.postfix... *** WARNING *** Found /etc/postfix/main.cf.SuSEconfig, exiting... *** WARNING *** How is that I should have done that editing ? I seem to remember, that it must not be done manually, but via yast. Is that right ? -- Med venlig hilsen / Best regards Erik Jakobsen DENMARK
Erik Jakobsen wrote:
Hi.
On my SuSE 10.1 I have manually changed the /etc/postfix/master.cf.
When I after ran SuSEconfig, I got this:
Executing /sbin/conf.d/SuSEconfig.postfix... *** WARNING *** Found /etc/postfix/main.cf.SuSEconfig, exiting... *** WARNING ***
How is that I should have done that editing ?
I seem to remember, that it must not be done manually, but via yast. Is that right ?
Hej Erik, I always edit my postfix config manually, so you definitely don't _have_ to use YaST. But I never run SuSEconfig afterwards either. /Per Jessen, Zürich
Per Jessen wrote:
Erik Jakobsen wrote:
Hi.
On my SuSE 10.1 I have manually changed the /etc/postfix/master.cf.
When I after ran SuSEconfig, I got this:
Executing /sbin/conf.d/SuSEconfig.postfix... *** WARNING *** Found /etc/postfix/main.cf.SuSEconfig, exiting... *** WARNING ***
How is that I should have done that editing ?
I seem to remember, that it must not be done manually, but via yast. Is that right ?
Hej Erik,
I always edit my postfix config manually, so you definitely don't _have_ to use YaST. But I never run SuSEconfig afterwards either.
/Per Jessen, Zürich
Hej Per. A good idea Per I have to approve the way you do it. That's the way to avoid seeing the warnings, and all is ok 8-) Ha en god dag. -- Med venlig hilsen / Best regards Erik Jakobsen DENMARK
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-05-24 at 08:56 +0200, Erik Jakobsen wrote:
A good idea Per I have to approve the way you do it. That's the way to avoid seeing the warnings, and all is ok 8-)
It doesn't matter. You can configure postfix manually; SuSEconfig notices that and refuses to configure it. Nothing wrong there: simply ignore the warning (it is a warning, after all, not an error). Yast will run SuSEconfig after any package addition, anyway. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEdEGTtTMYHG2NR9URAmHAAJ9aArcnl3Meo5fMlqQBu+/braFysQCgk6EV H2AXGWwoF5uNDfH5K2AkJZA= =kOKH -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2006-05-24 at 08:56 +0200, Erik Jakobsen wrote:
A good idea Per I have to approve the way you do it. That's the way to avoid seeing the warnings, and all is ok 8-)
It doesn't matter. You can configure postfix manually; SuSEconfig notices that and refuses to configure it. Nothing wrong there: simply ignore the warning (it is a warning, after all, not an error).
Yast will run SuSEconfig after any package addition, anyway.
- -- Cheers, Carlos Robinson
Thank you Carlos. -- Med venlig hilsen / Best regards Erik Jakobsen DENMARK
participants (3)
-
Carlos E. R.
-
Erik Jakobsen
-
Per Jessen