| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Mon, 23 Mar 92 08:56:06 -0500 To: Mack@rus.uni-stuttgart.de (Dieter Mack) Cc: danglert@source.asset.com Cc: info-afs@transarc.com In-Reply-To: Dieter Mack's message of Mon, 23 Mar 92 14:51:37 +0100, From: "Richard Basch" <basch@MIT.EDU> Date: Mon, 23 Mar 92 14:51:37 +0100 From: Mack@RUS.Uni-Stuttgart.DE (Dieter Mack) What I found out since, is, that the bosserver restarts without any problems as long as I start it up from a user shell (as root, of course), but dies with the "can't initialize rx" log message if started via /etc/inittab, so it appears to be a misbehavior of the old instance of bosserver, not the new one. Actually, what I discovered is that the "bosserver" somehow restarts because new processes are created (fileserver, ptserver, etc), but the bosserver seems to not be present. Given that the other logs have all been turned over and that there were graceful shutdowns/startups of each of the sub-processes, it seems that the bosserver somehow is trying to initialize the rx layer late. As I said, it is not consistent behavior. Personally, I have found the bosserver to die with the weekly restart and not when doing bos restart <server> -bosserver -Richard
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |