From grr Thu Feb 29 17:04:11 1996 Return-Path: grr Received: (from grr@localhost) by ector.cs.purdue.edu (8.7.3/PURDUE_CS-1.4) id RAA17352; Thu, 29 Feb 1996 17:03:17 -0500 (EST) Date: Thu, 29 Feb 1996 17:03:17 -0500 (EST) From: Gustavo Rodriguez-Rivera Message-Id: <199602292203.RAA17352@ector.cs.purdue.edu> To: 603, grr, trinkle Subject: rusers does not work for ector Content-Length: 980 It seems that rusers does not work with ector. I would recommend you to pass the remote host name as an argument to your rusers program and test it in any of the xinu machines. Do not test your program in ector. --Gustavo --- Included message ----- >From trinkle Thu Feb 29 16:20:48 1996 To: grr cc: software Subject: Re: [Purdue CS #1662] rusers in ector does not work... X-Request-Do: take Date: Thu, 29 Feb 1996 16:20:35 -0500 From: trinkle (Daniel Trinkle) Gustavo Rodriguez-Rivera (grr) writes: > Do you know why "rusers ector" does not work on any > machine? > > --Gustavo > Yes, there are so many users that the rpc.rusersd process gets a segmentation fault and dies before it generates the response. I'll look briefly at it, but if it's not easy to fix it will just remain that way. The workaround is to use finger -- not exactly the same, but kind of close. Since you have an ector account, you can also use "rsh ector /usr/ucb/users". Dan From grr Thu Feb 29 17:22:24 1996 Return-Path: grr Received: (from grr@localhost) by ector.cs.purdue.edu (8.7.3/PURDUE_CS-1.4) id RAA18649; Thu, 29 Feb 1996 17:21:39 -0500 (EST) Date: Thu, 29 Feb 1996 17:21:39 -0500 (EST) From: Gustavo Rodriguez-Rivera Message-Id: <199602292221.RAA18649@ector.cs.purdue.edu> To: 603, grr, trinkle Subject: rusers is now working in ector... Content-Length: 1060 Rusers is now working in ector thanks to Dan. ----- Included message ---- >From trinkle Thu Feb 29 17:13:46 1996 To: grr cc: software Subject: Re: [Purdue CS #1662] rusers in ector does not work... Date: Thu, 29 Feb 1996 17:13:37 -0500 From: trinkle (Daniel Trinkle) Gustavo Rodriguez-Rivera (grr) writes: > Do you know why "rusers ector" does not work on any > machine? > > --Gustavo The Solaris 2.3 source was not too hard to repair, so I fixed it and installed a test version on Ector (Solaris 2.4) and Labserver (Solaris 2.3). It actually was not directly related to the number of users on Ector, but the fact that the program was relying on the ut_syslen field being set to something useful in the /etc/utmpx file. It is supposed to be the length of the ut_host field, but the best I can tell, it has something to do with Elvis' current lattitude modulo the number of sunspots visible on Mars times the electrostatic charge on our cat (i.e. meaningless). SunSoft has yet to fully grasp the concept of the utmp (and utmpx) files. Dan From grr Fri Mar 1 11:54:50 1996 Return-Path: grr Received: (from grr@localhost) by ector.cs.purdue.edu (8.7.4/PURDUE_CS-1.4) id LAA20831; Fri, 1 Mar 1996 11:53:52 -0500 (EST) Date: Fri, 1 Mar 1996 11:53:52 -0500 (EST) From: Gustavo Rodriguez-Rivera Message-Id: <199603011653.LAA20831@ector.cs.purdue.edu> To: fresko Subject: Re: rusers proc. names Cc: 603, grr Status: R Content-Length: 279 > Do you know the difference between the 'names' and 'allnames' calls of > rusers? allnames returns not only the users that are currently ulogged in but also information of other users that are not logged in but have processes running in the system. Check utmp(4). --Gustavo From grr Thu Feb 29 14:38:29 1996 Return-Path: grr Received: (from grr@localhost) by ector.cs.purdue.edu (8.7.3/PURDUE_CS-1.4) id OAA05724; Thu, 29 Feb 1996 14:38:29 -0500 (EST) Date: Thu, 29 Feb 1996 14:38:29 -0500 (EST) From: Gustavo Rodriguez-Rivera Message-Id: <199602291938.OAA05724@ector.cs.purdue.edu> To: software Subject: rusers in ector does not work... Cc: grr Status: RO Content-Length: 73 Do you know why "rusers ector" does not work on any machine? --Gustavo From grr Fri Mar 1 11:29:16 1996 Return-Path: grr Received: (from grr@localhost) by ector.cs.purdue.edu (8.7.4/PURDUE_CS-1.4) id LAA18849; Fri, 1 Mar 1996 11:28:26 -0500 (EST) Date: Fri, 1 Mar 1996 11:28:26 -0500 (EST) From: Gustavo Rodriguez-Rivera Message-Id: <199603011628.LAA18849@ector.cs.purdue.edu> To: psk Subject: Re: rusers is now working in ector... Cc: 603, grr Status: RO Content-Length: 213 > Could you please let me know when > the project is due and also whether Russo has given phase 2 today in class. The project is due Tuesday March 12. Phase 2 is the same as phase 1 but using rpcgen. --Gustavo From ttd Fri Mar 1 11:36:43 1996 Return-Path: ttd@cs.purdue.edu Received: from pamela.cs.purdue.edu (pamela.cs.purdue.edu [128.10.8.49]) by ector.cs.purdue.edu (8.7.4/PURDUE_CS-1.4) with ESMTP id LAA19759 for ; Fri, 1 Mar 1996 11:36:42 -0500 (EST) Received: (from ttd@localhost) by pamela.cs.purdue.edu (8.7.4/PURDUE_CS-1.4) id LAA19553; Fri, 1 Mar 1996 11:36:40 -0500 (EST) From: "Tzvetan Todorov Drashansky" Message-Id: <9603011136.ZM19551@pamela.cs.purdue.edu> Date: Fri, 1 Mar 1996 11:36:39 -0500 In-Reply-To: Gustavo Rodriguez-Rivera "Re: rusers is now working in ector..." (Mar 1, 11:28am) References: <199603011628.LAA18849@ector.cs.purdue.edu> X-Mailer: Z-Mail (3.2.0 06sep94) To: Gustavo Rodriguez-Rivera Subject: project 2 phase 2 Cc: russo, bdd Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Status: RO Content-Length: 604 Hi Gustavo, The following e-mail prompted my question. > > Could you please let me know when > > the project is due and also whether Russo has given phase 2 today in class. > > The project is due Tuesday March 12. Phase 2 is the same as phase 1 but using > rpcgen. > Is this correct? I.e., is Phase 2 "Make an rusers client using rpcgen"? It was my understanding that Dr. Russo wanted us to make _both_ a client and a server with functionality of our choice (but with complicated data structures exchanged when an remote procedure is called). A clarification would be appreciated. Thanks, Tzvetan. From russo Fri Mar 1 11:40:22 1996 Return-Path: russo@cs.purdue.edu Received: from leonardo.cs.purdue.edu (root@leonardo.cs.purdue.edu [128.10.2.33]) by ector.cs.purdue.edu (8.7.4/PURDUE_CS-1.4) with ESMTP id LAA20104 for ; Fri, 1 Mar 1996 11:40:21 -0500 (EST) Received: from leonardo.cs.purdue.edu (russo@leonardo.cs.purdue.edu [128.211.1.133]) by leonardo.cs.purdue.edu (8.7.4/PURDUE_CS-1.4) with SMTP id LAA16942; Fri, 1 Mar 1996 11:40:16 -0500 (EST) Sender: russo Message-ID: <3137286E.37F2@cs.purdue.edu> Date: Fri, 01 Mar 1996 11:40:14 -0500 From: "Vincent F. Russo" Organization: Purdue University Department of Computer Science X-Mailer: Mozilla 2.0 (X11; I; SunOS 5.4 sun4m) MIME-Version: 1.0 To: Tzvetan Todorov Drashansky CC: Gustavo Rodriguez-Rivera , "Vincent F. Russo" , bdd Subject: Re: project 2 phase 2 References: <199603011628.LAA18849@ector.cs.purdue.edu> <9603011136.ZM19551@pamela.cs.purdue.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Status: RO Content-Length: 712 Tzvetan Todorov Drashansky wrote: > > Hi Gustavo, > > The following e-mail prompted my question. > > > > Could you please let me know when > > > the project is due and also whether Russo has given phase 2 today in class. > > > > The project is due Tuesday March 12. Phase 2 is the same as phase 1 but using > > rpcgen. > > > > Is this correct? I.e., is Phase 2 "Make an rusers client using rpcgen"? It was > my understanding that Dr. Russo wanted us to make _both_ a client and a server > with functionality of our choice (but with complicated data structures > exchanged when an remote procedure is called). A clarification would be > appreciated. Gustavo left class early. Tzventan's comment is correct. > I read chaper 4 of the rpc manual. There are top, intermediate, expert > levels of calls. Can I use top level functins clnt_create() to > finish my project, or should I implement my own clnt_create()? You may use clnt_create(). --Gustavo From grr Wed Mar 6 18:46:33 1996 Return-Path: grr Received: (from grr@localhost) by ector.cs.purdue.edu (8.7.4/PURDUE_CS-1.4) id SAA25288; Wed, 6 Mar 1996 18:45:44 -0500 (EST) Date: Wed, 6 Mar 1996 18:45:44 -0500 (EST) From: Gustavo Rodriguez-Rivera Message-Id: <199603062345.SAA25288@ector.cs.purdue.edu> To: 603, grr Subject: Use rpcgen... Content-Length: 271 I recommend you to run "rpcgen rusers.x" and see what generates. This will give you some ideas of how sun rpc works. Also don't forget to read the documentation in /u/u3/603/96spring/SUNWabsdk-ps/ps/NETP/ Chapters 3 and 4 are the most important. --Gustavo > When I try rpcgen I get an error: > > (xinu6) ~/cs603/proj2 > rpcgen /usr/include/rpcsvc/rusers.x > rpcgen: unable to open /usr/include/rpcsvc/rusers_xdr.c: Permission denied > (xinu6) ~/cs603/proj2 > Make a copy of rusers.x in the current directory. --Gustavo It has come to my attention that some people are printing the entire rpc manual. Please take into account that each page cost about one dollar and a piece of a tree. Make careful use of the printing facilities and just print the pages that you need. Look at the manual in the computer using ghostview. Please at least take a look at the content of what you print before printing it. My guess is that some people are printing pages that they will never read. --Gustavo