after installing f10beta (x86_64) from current boot.iso, the boot has a significant delay waiting for sendmail and sm-client to fail. the problem is not present after installing from live cd. of course, disabling the sendmail service skips the problem for now.
On Mon, Sep 29, 2008 at 02:44:07PM +0300, cornel panceac wrote:
after installing f10beta (x86_64) from current boot.iso, the boot has a significant delay waiting for sendmail and sm-client to fail.
The most likely reason is that somethig is misconfigured and attempts by sendmail to find a host name are failing and you are stuck on a timeout for that. Adding a name you are searching for to /etc/hosts would be one way to prevent this.
This was like that from "always".
Michal
should this happen on a default fedora install?
2008/9/29 Michal Jaegermann michal@harddata.com
On Mon, Sep 29, 2008 at 02:44:07PM +0300, cornel panceac wrote:
after installing f10beta (x86_64) from current boot.iso, the boot has a significant delay waiting for sendmail and sm-client to fail.
The most likely reason is that somethig is misconfigured and attempts by sendmail to find a host name are failing and you are stuck on a timeout for that. Adding a name you are searching for to /etc/hosts would be one way to prevent this.
This was like that from "always".
Michal
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
Michal Jaegermann wrote:
On Mon, Sep 29, 2008 at 02:44:07PM +0300, cornel panceac wrote:
after installing f10beta (x86_64) from current boot.iso, the boot has a significant delay waiting for sendmail and sm-client to fail.
The most likely reason is that somethig is misconfigured and attempts by sendmail to find a host name are failing and you are stuck on a timeout for that. Adding a name you are searching for to /etc/hosts would be one way to prevent this.
This was like that from "always".
Michal
Please have a look at https://bugzilla.redhat.com/show_bug.cgi?id=464191
Thanks, Thomas
2008/9/29 Thomas Woerner twoerner@redhat.com
Michal Jaegermann wrote:
On Mon, Sep 29, 2008 at 02:44:07PM +0300, cornel panceac wrote:
after installing f10beta (x86_64) from current boot.iso, the boot has a significant delay waiting for sendmail and sm-client to fail.
The most likely reason is that somethig is misconfigured and attempts by sendmail to find a host name are failing and you are stuck on a timeout for that. Adding a name you are searching for to /etc/hosts would be one way to prevent this.
This was like that from "always".
Michal
Please have a look at
i suppose this is the problem, however, anaconda should check the validity of the user input, imho.
Thanks, Thomas
-- Thomas Woerner Software Engineer Phone: +49-711-96437-310 Red Hat GmbH Fax : +49-711-96437-111 Hauptstaetterstr. 58 Email: Thomas Woerner twoerner@redhat.com D-70178 Stuttgart Web : http://www.redhat.de/
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
ronald warsow told me that a test for sendmail config is:
sendmail -d0 < /dev/null
indeed, in my case the output was incomplete, it has no fqdn there. however, fixing /etc/hosts did not solve the problem. i searched deeper and i've found the problem in /etc/sysconfig/network fixing the latter file fixed sendmail start even if /etc/hosts was left unfixed.
thank you all for help.
2008/9/29 cornel panceac cpanceac@gmail.com
2008/9/29 Thomas Woerner twoerner@redhat.com
Michal Jaegermann wrote:
On Mon, Sep 29, 2008 at 02:44:07PM +0300, cornel panceac wrote:
after installing f10beta (x86_64) from current boot.iso, the boot has a significant delay waiting for sendmail and sm-client to fail.
The most likely reason is that somethig is misconfigured and attempts by sendmail to find a host name are failing and you are stuck on a timeout for that. Adding a name you are searching for to /etc/hosts would be one way to prevent this.
This was like that from "always".
Michal
Please have a look at
i suppose this is the problem, however, anaconda should check the validity of the user input, imho.
Thanks, Thomas
-- Thomas Woerner Software Engineer Phone: +49-711-96437-310 Red Hat GmbH Fax : +49-711-96437-111 Hauptstaetterstr. 58 Email: Thomas Woerner twoerner@redhat.com D-70178 Stuttgart Web : http://www.redhat.de/
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
-- Linux counter #213090
cornel panceac wrote:
ronald warsow told me that a test for sendmail config is:
sendmail -d0 < /dev/null
indeed, in my case the output was incomplete, it has no fqdn there. however, fixing /etc/hosts did not solve the problem. i searched deeper and i've found the problem in /etc/sysconfig/network fixing the latter file fixed sendmail start even if /etc/hosts was left unfixed.
thank you all for help.
And what have you fixed there?
Thomas
2008/9/30 Thomas Woerner twoerner@redhat.com
cornel panceac wrote:
ronald warsow told me that a test for sendmail config is:
sendmail -d0 < /dev/null
indeed, in my case the output was incomplete, it has no fqdn there. however, fixing /etc/hosts did not solve the problem. i searched deeper and i've found the problem in /etc/sysconfig/network fixing the latter file fixed sendmail start even if /etc/hosts was left unfixed.
thank you all for help.
And what have you fixed there?
replaced guzu64 with guzu64.undome.niu
Thomas
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
2008/9/30 cornel panceac cpanceac@gmail.com
2008/9/30 Thomas Woerner twoerner@redhat.com
cornel panceac wrote:
ronald warsow told me that a test for sendmail config is:
sendmail -d0 < /dev/null
indeed, in my case the output was incomplete, it has no fqdn there. however, fixing /etc/hosts did not solve the problem. i searched deeper and i've found the problem in /etc/sysconfig/network fixing the latter file fixed sendmail start even if /etc/hosts was left unfixed.
thank you all for help.
And what have you fixed there?
replaced guzu64 with guzu64.undome.niu
the problem seems to still be present on updated f10 preview.
Thomas
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
-- Linux counter #213090
-
cornel panceac -
Michal Jaegermann -
Thomas Woerner