Hi All, I ran this through a translator, here is the engligh of it. Don It is Imai. 9.1 SuSEfirewall2 (/etc/sysconfig/SuSEfirewall2) rustling fumbling, the て you became aware, it is, but... . FW_SERVICES_EXT_RPC (one way there is no port number, it is with rpcinfo command issuing, in order the type which decides the port number which it passes) with to pass through the relationship of NIS, what it sets is to call, but at the time of Linux starting network before starting, the processing per SuSEfirewall2_init (really it is inside /sbin/SuSEfirewall2 command don't you think?) with very rpcinfo command to issue, making the message which the ちゃ っ て る to seem the port mapper - with you cannot connect and how say, it increases. The port mapper - being to be before the starting, such error coming out is natural, but. After, Squid using, the る it is with FW_SERVICE_SQUID=" Yes" When it does and solves "Squid starting around SuSEfilrewall2_init and SuSEfirewall2_setup, increase it is" with the message which you say coming out, however the る it is, if this you mention just a little stupidity, don't you think? it is stupid. FW_SERVICES_EXT_RPC and others becoming the same 9.1 NIS servers with seeing, and SuSEfirewall2 moving with the る machine, in case of the る, unless ypbind it is moved with the NIS server, it denies the connection from クライア ント and the ちゃ っ て る way the air.... . If (you mention the proper, it is proper, but....) That this of /etc/sysconfig/SuSEfirewall2 you can fumble, but it is, it is a little sad not to be able to correspond with, don't you think? is. 9.2 So becoming dyspepsia, so it puts out.... . -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Imai Yutaka mail: Maimai@coral.ocn.ne.jpweb: Http: //www10.ocn.ne.jp/ - Masimai/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --Check the List-Unsubscribe header to unsubscribe For additional comman ds and email: Suse-amd64-help@suse.com -----Original Message----- From: Masaru Imai [mailto:maimai@coral.ocn.ne.jp] Sent: Friday, October 29, 2004 11:34 AM To: suse-amd64@suse.com Subject: [suse-amd64] SuSEfirewall2で気になったこと 今井です。 9.1のSuSEfirewall2(/etc/sysconfig/SuSEfirewall2)をごそごそいじってて 気づいたんですが....。 FW_SERVICES_EXT_RPC(ポート番号が一意じゃないんでrpcinfoコマンド 発行して通すポート番号を決定するタイプ)でNIS関係を通す様に設定したの はいいんですが、Linux起動時にネットワーク起動する前にSuSEfirewall2_init あたりの処理(実際は/sbin/SuSEfirewall2コマンド内部ですね)でどうもrpcinfo コマンド発行しちゃってるらしくポートマッパーと接続できないなんていうメッセージ を出してくれてます。 ポートマッパー起動前なのでそういうエラーが出るのも当り前ではありますが。 あと、Squid使ってるんでFW_SERVICE_SQUID="yes"にしとくと SuSEfilrewall2_init、SuSEfirewall2_setup辺りで「Squid起動してません」と いうメッセージ出てきてるんですけどこれもちょっと間抜けと言えば間抜けですね。 FW_SERVICES_EXT_RPCがらみで同じ9.1のNISサーバーとなってるマシンでも SuSEfirewall2動かしてる場合、NISサーバーでもypbind動かしてないとクライア ントからの接続を拒否しちゃってる様な気が.....。(当然と言えば当然ですが....) /etc/sysconfig/SuSEfirewall2あれこれいじれるんだけどyastで対応しきれて ないのが少し悲しいですね。9.2でも消化不良になってそうだし.....。 -- ‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾ 今井 優 mail: maimai@coral.ocn.ne.jp web: http://www10.ocn.ne.jp/‾masimai/ ‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾ -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com