Re: 2.6 device node help
I don't think you're on crack, but the book might be. 4,64 is a UART class serial line. Not likely your zSeries will have that. But all HW have 5,1 console. Well, neither is on crack. The 3215/sclp console driver use 4,64 as device node, so the dd-book is correct. But nevertheless you have to use 5,1 for /dev/console. The device that hides behind 5,1 is a redirector to the real console. blue skies, Martin Linux/390 Design Development, IBM Deutschland Entwicklung GmbH Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247 E-Mail: [EMAIL PROTECTED] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 2.6 device node help
Richard Troth wrote: Adam Thornton wote: OK, so, am I on CRACK or does the Linux 2.6 device drivers book say to create 4,64 ? I don't think you're on crack, but the book might be. 4,64 is a UART class serial line. Not likely your zSeries will have that. But all HW have 5,1 console. On zSeries, the 3215 terminal device driver (VM) and the SCLP line-mode terminal driver (LPAR) are implemented as ttyS0 (4,64). Device number (5,1) is the console terminal device (commonly /dev/console) which is required by the init process for input/output. The following should fix the problem: mknod /dev/console c 5 1 Regards, Peter Oberparleiter -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Monthly forehead bruising: inittab ctrlaltdel
David Boyes wrote: Given that I seem to have that right and seem to be at a current-enough (too current?) level of SLES 8, what else do I look for? I'm kind of puzzled what you're asking. Is it not working, or is it doing something weird? I'll go with, It's doing something weird. At the end of the timeout period, the kernel logs the virtual machine off. However, the shutdown command has not run. That it logs itself off tells me that something is happening. That shutdown never runs tells me that something weird is happening (or something good isn't happening). That's what makes me suspect a syntax issue: the kernel is trying to do something, but it's getting lost along the way and not taking the path it should. Mark's reference to telinit q wasn't directly relevant; I've re-booted this image several times after less-than-graceful responses to SIGNALs SHUTDOWN. However, that got me thinking about the runlevel, which, when I checked it, was unknown. If I init 3 and then test the SIGNAL SHUTDOWN, it works as expected. So, my next puzzle is, what's with the unknown runlevel? Or, just how screwed up is this particular Linux image? Fortunately, it's my test image. I haven't rebuilt it in a few weeks; must be time to do so. :-) -- db Nick -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Monthly forehead bruising: inittab ctrlaltdel
It worked for us pretty much as advertised. Have you tried issuing the signal with the console logged on so you can watch the messages? Or use a program like track. You should get a message from the kernel that the signal was caught even if the script doesn't run: 09:06:05 CAD: Sending SIGINT to PID 1... Apr 27 09:06:05 lnxsp3t kernel: CAD: Sending SIGINT to PID 1... Message from [EMAIL PROTECTED] at Tue Apr 27 09:06:05 2004 ... lnxsp3t kernel: CAD: Sending SIGINT to PID 1... -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Nick Laflamme Sent: Tuesday, April 27, 2004 8:56 AM To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] Monthly forehead bruising: inittab ctrlaltdel David Boyes wrote: Given that I seem to have that right and seem to be at a current-enough (too current?) level of SLES 8, what else do I look for? I'm kind of puzzled what you're asking. Is it not working, or is it doing something weird? I'll go with, It's doing something weird. At the end of the timeout period, the kernel logs the virtual machine off. However, the shutdown command has not run. That it logs itself off tells me that something is happening. That shutdown never runs tells me that something weird is happening (or something good isn't happening). That's what makes me suspect a syntax issue: the kernel is trying to do something, but it's getting lost along the way and not taking the path it should. Mark's reference to telinit q wasn't directly relevant; I've re-booted this image several times after less-than-graceful responses to SIGNALs SHUTDOWN. However, that got me thinking about the runlevel, which, when I checked it, was unknown. If I init 3 and then test the SIGNAL SHUTDOWN, it works as expected. So, my next puzzle is, what's with the unknown runlevel? Or, just how screwed up is this particular Linux image? Fortunately, it's my test image. I haven't rebuilt it in a few weeks; must be time to do so. :-) -- db Nick -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 == If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ == -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
New England Users of VM (NEUVM) Spring Meeting - May 18, 2004
Cross-posted on NEUVM-L, VMESA-L and LINUX-390 - feel free to forward as appropriate. Greetings! NEUVM will be holding it's Spring Meeting on May 18, 2004 at Lombardo's in Randolph, Massachusetts. For meeting details and online registration click here: http://www.neuvm.org/include.php?include=./meeting-0002/agenda.php We've updated the agenda since last Friday's announcement to include Gerard Shockley's presentation on running Tomcast on SuSE Z/Linux: User Experience: Tomcat on SuSE z/Linux Gerard Shockley, Boston University The presentation is geared toward new sites running on z/Series and performs a brief introduction of z/Series strategy and platform strengths, and demonstrates an actual project flow and technical details on activating Tomcat with SSL support and a servelet application. Included in the discussion are system administration skill sets required for z/LINUX and how one begins to port to z/LINUX. Once again, registration is FREE and includes a breakfast buffeet and fabulous Lombardo's luncheon, featuring your choice of Roast Prime Rib of Beef or New England Roasted Turkey Dinner! Advance online registration is required, and we need to determine a head-count for meals so please register ASAP. Register online here: http://www.neuvm.org/register.php Michael Coffin New England Users of VM (NEUVM) 289 Park Street - PMB 123 Stoughton, Massachusetts 02072 Voice: (781) 344-9837FAX: (781) 344-7683 [EMAIL PROTECTED] www.NEUVM.org -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Linux NFS shares and Windoze interoperability
After some initial poking and prodding and smacking things about, I've gotten windows (using the Windows Services for Unix package from microsoft) to see and navigate NFS mounted shares, but It seems that I had to more that I feel was necessary in order to make it work. Initially, linux complained when my windows PC tried to get the share: Apr 26 12:26:43 rockhopper rpc.mountd: can't get hostname of 137.70.103.112 That turned out to be the DHCP assigned IP address for my windows machine. As soon as I got a static IP with a DNS entry assigned, all was well. I altered the /etc/exports to recognize the DNS entry assigned to this and I could make it navigate the tree. I have yet to be able to make the mount command, which is replaced with something new when you install Windows Services for Unix, to actually mount the NFS share, but I have been able to use 'my network places' to see the share on the target machine. I think however it is using UDP. When I started doing this, these messages started appearing in my log about every 10 minutes. Apr 27 08:30:46 rockhopper inetd[83]: netbios-ns/udp server failing (looping), service terminate Anyway, is there something I need to do differently in my exports file to not require DNS reverse lookup of an inbound host? My exports file looks like this. For this test (after I got the static IP) I added gsopdwdf911 (my DNS name. Strange name I know) to one single share, and I can get there no problem usning 'my network places' I'm just wondering about the wisdom of including IP address ranges, or if that is even going to work # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. /images itasca(ro) calhoun(ro) pepin(ro) phalen(ro) nokomis(ro) pequot(ro) /images/ibm/Msg_broker/db2 itasca(ro) calhoun(ro) pepin(ro) phalen(ro) nokomis(ro) pequot(ro) gsopdwdf911(ro) /images/ibm/Msg_broker/was_MQ itasca(ro) calhoun(ro) pepin(ro) phalen(ro) nokomis(ro) pequot(ro) /images/ibm/Msg_broker/was_MB itasca(ro) calhoun(ro) pepin(ro) phalen(ro) nokomis(ro) pequot(ro) -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Monthly forehead bruising: inittab ctrlaltdel
Nick Laflamme wrote: So, my next puzzle is, what's with the unknown runlevel? Or, just how screwed up is this particular Linux image? Fortunately, it's my test image. I haven't rebuilt it in a few weeks; must be time to do so. :-) The 'runlevel' command should tell you... I am not sure whether this has been brought up again in this thread, but one popular and effective way to mess up the SLES 8 install is to forget running the YaST.sshinstall after the first boot. That's the portion that asks you (again) to set the root password, add other users, etc. You're prompted to run that by some messages during the shutdown after the first time you ran YaST, and it is easy to miss. The system appears to be sort of working but does strange things. Rob -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux NFS shares and Windoze interoperability
James, since you said you installed Unix services, do you have an 'NFS network' entry under 'Entire Network' (under 'My Network Places')? IOW, My Network Places -- Entire Network -- NFS Network. If so did you right click to add a new entry under NFS Network? I used the static IP of my Linux machine when I config'd it for NFS Network. I also made the necessary changes to the Linux side in /etc/exports and all worked well, albeit very slowly. I wasn't going to implement this into production, so I wasn't to worried about the speed. But since the subject has been brought up does anyone know why the reponse time would be so slow? Steve Gentry Lafayette Life Ins. Co. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux NFS shares and Windoze interoperability
I have been unable to get that to actually see the linux instances on the mainframe. If sees the linux PC in my cube which is also running NFS, and it put that in the 'default lan' group. When I attempt to do the 'add' part it pops up a box saying add/remove NFS LAN's, so I click add. I then get a box that says Add Broadcast Lan (not what I would expect but I go with it) I wants a name to call it, so I put in nokomis. My linux guest running NFS. Then It wants IP address of any Host in the LAN - meaning what exactly? Dunno. I put the IP address of 'nokomis' in there Then it wants the subnet mask, and I enter that. Then it somehow gets the broadcast address by itself, and from what I see it is getting it wrong, as it's on a diff subnet. The IP address of nokimis is 137.70.100.134, and the net mask is 255.255.254.0 but the broadcast address is being returned as 137.70.101.255. As I vaguely recall, the 101 had somethign to do with the VIPA setup on our OSA cards... I am confused here. Steve Gentry Stephen_R_Gentry @LafayetteLife.co To m[EMAIL PROTECTED] Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Re: Linux NFS shares and Windoze interoperability 04/27/2004 09:08 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU James, since you said you installed Unix services, do you have an 'NFS network' entry under 'Entire Network' (under 'My Network Places')? IOW, My Network Places -- Entire Network -- NFS Network. If so did you right click to add a new entry under NFS Network? I used the static IP of my Linux machine when I config'd it for NFS Network. I also made the necessary changes to the Linux side in /etc/exports and all worked well, albeit very slowly. I wasn't going to implement this into production, so I wasn't to worried about the speed. But since the subject has been brought up does anyone know why the reponse time would be so slow? Steve Gentry Lafayette Life Ins. Co. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux NFS shares and Windoze interoperability
Initially, linux complained when my windows PC tried to get the share: Apr 26 12:26:43 rockhopper rpc.mountd: can't get hostname of 137.70.103.112 As it should -- this is a security feature. It's actually creating an audit trail for your actions and couldn't get a hostname to log it in the audit trail. It's a transient complaint -- it went ahead and logged the IP address, but the permanent fix is to get DNS names assigned to your DHCP pools (example: dhcp-137-70-103-112.foo.bar.edu). It's a good idea anyway, and it makes tracking troublemakers a lot easier. I have yet to be able to make the mount command, which is replaced with something new when you install Windows Services for Unix, to actually mount the NFS share, but I have been able to use 'my network places' to see the share on the target machine. I think however it is using UDP. When I started doing this, these messages started appearing in my log about every 10 minutes. Apr 27 08:30:46 rockhopper inetd[83]: netbios-ns/udp server failing (looping), service terminate Nope. The Windows code is looking for a WINS server (netbios-ns is the official IETF name for WINS). rockhopper has a entry in /etc/services for the WINS port, which doesn't appear to be configured on this machine (causing it to die), and inetd eventually decides that that service is broken and it's going to ignore requests for it (thus the message). Installing/configuring Samba and enabling WINS support will cause this message to go away. Why the Windows code wants it, I can't imagine... Anyway, is there something I need to do differently in my exports file to not require DNS reverse lookup of an inbound host? No. Get your network people to put proper reverse mappings in your DNS for their DHCP pools. This problem will occur in other services, and it's probably affecting the performance of your existing services as well (you're waiting for reverse resolution on every connect if you have systems or services that are trying to be more secure and log things). You might as well fix the problem instead of the symptoms. I'm just wondering about the wisdom of including IP address ranges, or if that is even going to work It will work, but it's a problem waiting to happen. Get the DNS fixed. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux NFS shares and Windoze interoperability
I also made the necessary changes to the Linux side in /etc/exports and all worked well, albeit very slowly. I wasn't going to implement this into production, so I wasn't to worried about the speed. But since the subject has been brought up does anyone know why the reponse time would be so slow? Does your NFS client have a reverse mapping in DNS for it's IP address? If not, you're probably experiencing some of the delays I mentioned in my response to James. The Unix world cares about stuff like this (discounting my normal healthy network admin fascism about if it ain't in DNS, it probably isn't something I should be talking to). Another possibility: NFS is stateless, and some of it's security is based on IP address. It does a lot of DNS lookups, and you can dramatically change it's performance by making sure forward and reverse DNS is correct. It (NFS Services) isn't great code -- the phrase MS Porcine Choral Society comes to mind. There's a lot of (IMHO) unnecessary mapping going on in the filesystem drivers, and it's in no particular hurry to do things efficiently. -- db -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux NFS shares and Windoze interoperability
Sounds like you followed the correct steps on the PC side. We keep our network addressing pretty simple. Whereas, my pc is on network 10.53.x.x and zLinux is 10.140.x.x Like I said, I have no problems seeing it and getting to it, but response time can be a little slow. This slowness is unrelated to how busy the box is at the time. BTW, I am running RH EL 2.85 (taroon). Steve James Melin [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 04/27/2004 09:48 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: Linux NFS shares and Windoze interoperability I have been unable to get that to actually see the linux instances on the mainframe. If sees the linux PC in my cube which is also running NFS, and it put that in the 'default lan' group. When I attempt to do the 'add' part it pops up a box saying add/remove NFS LAN's, so I click add. I then get a box that says Add Broadcast Lan (not what I would expect but I go with it) I wants a name to call it, so I put in nokomis. My linux guest running NFS. Then It wants IP address of any Host in the LAN - meaning what exactly? Dunno. I put the IP address of 'nokomis' in there Then it wants the subnet mask, and I enter that. Then it somehow gets the broadcast address by itself, and from what I see it is getting it wrong, as it's on a diff subnet. The IP address of nokimis is 137.70.100.134, and the net mask is 255.255.254.0 but the broadcast address is being returned as 137.70.101.255. As I vaguely recall, the 101 had somethign to do with the VIPA setup on our OSA cards... I am confused here. Steve Gentry Stephen_R_Gentry @LafayetteLife.co To m[EMAIL PROTECTED] Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Re: Linux NFS shares and Windoze interoperability 04/27/2004 09:08 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU James, since you said you installed Unix services, do you have an 'NFS network' entry under 'Entire Network' (under 'My Network Places')? IOW, My Network Places -- Entire Network -- NFS Network. If so did you right click to add a new entry under NFS Network? I used the static IP of my Linux machine when I config'd it for NFS Network. I also made the necessary changes to the Linux side in /etc/exports and all worked well, albeit very slowly. I wasn't going to implement this into production, so I wasn't to worried about the speed. But since the subject has been brought up does anyone know why the reponse time would be so slow? Steve Gentry Lafayette Life Ins. Co. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux NFS shares and Windoze interoperability
Your broadcast address looks right to me. I don't know if I can explain this well, but I will try. The subnet mask that you specified says that the subnet has a 9 bit host address. Thus the last 9 bits of the IP address specifies the host on the subnet. The broadcast address on this subnet has the last 9 bits on. In general the broadcast address has all bits of the host part on. Therefore the broadcast address is the upper 23 bits of the IP for the subnet with all ones for the host part, which is 137.70.101.255. The 101 is due to the fact that the last bit is on for the broadcast address. Note that 101 in binary is 01100101 - that last bit is one. A 100 would be 01100100. Now if you are sure that the broadcast address is wrong, then your subnet mask must be wrong. -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 7:48 AM To: [EMAIL PROTECTED] Subject: Re: Linux NFS shares and Windoze interoperability I have been unable to get that to actually see the linux instances on the mainframe. If sees the linux PC in my cube which is also running NFS, and it put that in the 'default lan' group. When I attempt to do the 'add' part it pops up a box saying add/remove NFS LAN's, so I click add. I then get a box that says Add Broadcast Lan (not what I would expect but I go with it) I wants a name to call it, so I put in nokomis. My linux guest running NFS. Then It wants IP address of any Host in the LAN - meaning what exactly? Dunno. I put the IP address of 'nokomis' in there Then it wants the subnet mask, and I enter that. Then it somehow gets the broadcast address by itself, and from what I see it is getting it wrong, as it's on a diff subnet. The IP address of nokimis is 137.70.100.134, and the net mask is 255.255.254.0 but the broadcast address is being returned as 137.70.101.255. As I vaguely recall, the 101 had somethign to do with the VIPA setup on our OSA cards... I am confused here. Steve Gentry Stephen_R_Gentry @LafayetteLife.co To m[EMAIL PROTECTED] Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Re: Linux NFS shares and Windoze interoperability 04/27/2004 09:08 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU James, since you said you installed Unix services, do you have an 'NFS network' entry under 'Entire Network' (under 'My Network Places')? IOW, My Network Places -- Entire Network -- NFS Network. If so did you right click to add a new entry under NFS Network? I used the static IP of my Linux machine when I config'd it for NFS Network. I also made the necessary changes to the Linux side in /etc/exports and all worked well, albeit very slowly. I wasn't going to implement this into production, so I wasn't to worried about the speed. But since the subject has been brought up does anyone know why the reponse time would be so slow? Steve Gentry Lafayette Life Ins. Co. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux NFS shares and Windoze interoperability
Of course, now I cant remember how to get linux to barf up the broadcast address it is using, but if memory serves, for all my linuxes, the IP addresses are 137.70.100.xxx and the default gateway is 137.70.100.3, the netmask is set to 255.255.254.0. We orignally had a netmask of 255.255.255.0 but I changed to to ...254.0 per my network group after the install. The broadcast address that was set at install time was, I'm quite sure 137.70.100.255. So what is the implication of changing the netmask after the install? Is that part of what is causing this? Curiously, while doing the'my network places'NFS Nework---add/remove NFS LANs fails, entering the DNS name as \\nokomis in the address bar DOES in fact pull up the NFS shares on that machine and I can navigate them. So that's a plus. Fargusson.Alan [EMAIL PROTECTED] tb.ca.gov To Sent by: Linux on [EMAIL PROTECTED] 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: Linux NFS shares and Windoze interoperability 04/27/2004 10:36 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Your broadcast address looks right to me. I don't know if I can explain this well, but I will try. The subnet mask that you specified says that the subnet has a 9 bit host address. Thus the last 9 bits of the IP address specifies the host on the subnet. The broadcast address on this subnet has the last 9 bits on. In general the broadcast address has all bits of the host part on. Therefore the broadcast address is the upper 23 bits of the IP for the subnet with all ones for the host part, which is 137.70.101.255. The 101 is due to the fact that the last bit is on for the broadcast address. Note that 101 in binary is 01100101 - that last bit is one. A 100 would be 01100100. Now if you are sure that the broadcast address is wrong, then your subnet mask must be wrong. -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 7:48 AM To: [EMAIL PROTECTED] Subject: Re: Linux NFS shares and Windoze interoperability I have been unable to get that to actually see the linux instances on the mainframe. If sees the linux PC in my cube which is also running NFS, and it put that in the 'default lan' group. When I attempt to do the 'add' part it pops up a box saying add/remove NFS LAN's, so I click add. I then get a box that says Add Broadcast Lan (not what I would expect but I go with it) I wants a name to call it, so I put in nokomis. My linux guest running NFS. Then It wants IP address of any Host in the LAN - meaning what exactly? Dunno. I put the IP address of 'nokomis' in there Then it wants the subnet mask, and I enter that. Then it somehow gets the broadcast address by itself, and from what I see it is getting it wrong, as it's on a diff subnet. The IP address of nokimis is 137.70.100.134, and the net mask is 255.255.254.0 but the broadcast address is being returned as 137.70.101.255. As I vaguely recall, the 101 had somethign to do with the VIPA setup on our OSA cards... I am confused here. Steve Gentry Stephen_R_Gentry @LafayetteLife.co To m[EMAIL PROTECTED] Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Re: Linux NFS shares and Windoze interoperability 04/27/2004 09:08 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU James, since you said you installed Unix services, do you have an 'NFS network' entry under 'Entire Network' (under 'My Network Places')? IOW, My Network Places -- Entire Network -- NFS Network. If so did you right click to add a new entry under NFS Network? I used the static IP of my Linux machine when I config'd it for NFS Network. I also made the necessary changes to the Linux side in /etc/exports and all worked well, albeit very slowly. I wasn't going to implement this into production, so I wasn't to worried about the speed. But since the subject has been brought up does anyone know why the reponse time would be so slow? Steve Gentry Lafayette Life Ins. Co. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
Re: Linux NFS shares and Windoze interoperability
On Tue, 2004-04-27 at 12:36, James Melin wrote: Of course, now I cant remember how to get linux to barf up the broadcast address it is using, but if memory serves, for all my linuxes, the IP addresses are 137.70.100.xxx and the default gateway is 137.70.100.3, the netmask is set to 255.255.254.0. We orignally had a netmask of 255.255.255.0 but I changed to to ...254.0 per my network group after the install. The broadcast address that was set at install time was, I'm quite sure 137.70.100.255. So what is the implication of changing the netmask after the install? Is that part of what is causing this? Yep. Your network just got wider. Your new correct broadcast address should be 137.70.101.255. Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux NFS shares and Windoze interoperability
now I cant remember how to get linux to barf up the broadcast address it is using, Try issuing the command ifconfig -- it should tell you. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: James Melin Reply To: Linux on 390 Port Sent: Tuesday, April 27, 2004 10:36 AM To: [EMAIL PROTECTED] Subject: Re: Linux NFS shares and Windoze interoperability Of course, now I cant remember how to get linux to barf up the broadcast address it is using, but if memory serves, for all my linuxes, the IP addresses are 137.70.100.xxx and the default gateway is 137.70.100.3, the netmask is set to 255.255.254.0. We orignally had a netmask of 255.255.255.0 but I changed to to ...254.0 per my network group after the install. The broadcast address that was set at install time was, I'm quite sure 137.70.100.255. So what is the implication of changing the netmask after the install? Is that part of what is causing this? Curiously, while doing the'my network places'NFS Nework---add/remove NFS LANs fails, entering the DNS name as \\nokomis in the address bar DOES in fact pull up the NFS shares on that machine and I can navigate them. So that's a plus. Fargusson.Alan [EMAIL PROTECTED] tb.ca.gov To Sent by: Linux on [EMAIL PROTECTED] 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: Linux NFS shares and Windoze interoperability 04/27/2004 10:36 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Your broadcast address looks right to me. I don't know if I can explain this well, but I will try. The subnet mask that you specified says that the subnet has a 9 bit host address. Thus the last 9 bits of the IP address specifies the host on the subnet. The broadcast address on this subnet has the last 9 bits on. In general the broadcast address has all bits of the host part on. Therefore the broadcast address is the upper 23 bits of the IP for the subnet with all ones for the host part, which is 137.70.101.255. The 101 is due to the fact that the last bit is on for the broadcast address. Note that 101 in binary is 01100101 - that last bit is one. A 100 would be 01100100. Now if you are sure that the broadcast address is wrong, then your subnet mask must be wrong. -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 7:48 AM To: [EMAIL PROTECTED] Subject: Re: Linux NFS shares and Windoze interoperability I have been unable to get that to actually see the linux instances on the mainframe. If sees the linux PC in my cube which is also running NFS, and it put that in the 'default lan' group. When I attempt to do the 'add' part it pops up a box saying add/remove NFS LAN's, so I click add. I then get a box that says Add Broadcast Lan (not what I would expect but I go with it) I wants a name to call it, so I put in nokomis. My linux guest running NFS. Then It wants IP address of any Host in the LAN - meaning what exactly? Dunno. I put the IP address of 'nokomis' in there Then it wants the subnet mask, and I enter that. Then it somehow gets the broadcast address by itself, and from what I see it is getting it wrong, as it's on a diff subnet. The IP address of nokimis is 137.70.100.134, and the net mask is 255.255.254.0 but the broadcast address is being returned as 137.70.101.255. As I vaguely recall, the 101 had somethign to do with the VIPA setup on our OSA cards... I am confused here. Steve Gentry Stephen_R_Gentry @LafayetteLife.co To m[EMAIL PROTECTED] Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Re: Linux NFS shares and Windoze interoperability 04/27/2004 09:08 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU
Re: Linux NFS shares and Windoze interoperability
I was finally able to get it to tell me what broadcast address it was using, and yes infact it is now using 101.255. I cannot tell you if it was using 100.255 previously with the 255.255.255.0 NM. Fargusson.Alan [EMAIL PROTECTED] tb.ca.gov To Sent by: Linux on [EMAIL PROTECTED] 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: Linux NFS shares and Windoze interoperability 04/27/2004 10:36 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Your broadcast address looks right to me. I don't know if I can explain this well, but I will try. The subnet mask that you specified says that the subnet has a 9 bit host address. Thus the last 9 bits of the IP address specifies the host on the subnet. The broadcast address on this subnet has the last 9 bits on. In general the broadcast address has all bits of the host part on. Therefore the broadcast address is the upper 23 bits of the IP for the subnet with all ones for the host part, which is 137.70.101.255. The 101 is due to the fact that the last bit is on for the broadcast address. Note that 101 in binary is 01100101 - that last bit is one. A 100 would be 01100100. Now if you are sure that the broadcast address is wrong, then your subnet mask must be wrong. -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 7:48 AM To: [EMAIL PROTECTED] Subject: Re: Linux NFS shares and Windoze interoperability I have been unable to get that to actually see the linux instances on the mainframe. If sees the linux PC in my cube which is also running NFS, and it put that in the 'default lan' group. When I attempt to do the 'add' part it pops up a box saying add/remove NFS LAN's, so I click add. I then get a box that says Add Broadcast Lan (not what I would expect but I go with it) I wants a name to call it, so I put in nokomis. My linux guest running NFS. Then It wants IP address of any Host in the LAN - meaning what exactly? Dunno. I put the IP address of 'nokomis' in there Then it wants the subnet mask, and I enter that. Then it somehow gets the broadcast address by itself, and from what I see it is getting it wrong, as it's on a diff subnet. The IP address of nokimis is 137.70.100.134, and the net mask is 255.255.254.0 but the broadcast address is being returned as 137.70.101.255. As I vaguely recall, the 101 had somethign to do with the VIPA setup on our OSA cards... I am confused here. Steve Gentry Stephen_R_Gentry @LafayetteLife.co To m[EMAIL PROTECTED] Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Re: Linux NFS shares and Windoze interoperability 04/27/2004 09:08 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU James, since you said you installed Unix services, do you have an 'NFS network' entry under 'Entire Network' (under 'My Network Places')? IOW, My Network Places -- Entire Network -- NFS Network. If so did you right click to add a new entry under NFS Network? I used the static IP of my Linux machine when I config'd it for NFS Network. I also made the necessary changes to the Linux side in /etc/exports and all worked well, albeit very slowly. I wasn't going to implement this into production, so I wasn't to worried about the speed. But since the subject has been brought up does anyone know why the reponse time would be so slow? Steve Gentry Lafayette Life Ins. Co. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Monthly forehead bruising: inittab ctrlaltdel
Well, that would only leave 0 and 6 (or unknown as he's reporting), either of which would mean the system wasn't very usable at that moment. :) Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Tuesday, April 27, 2004 12:55 AM To: [EMAIL PROTECTED] Subject: Re: Monthly forehead bruising: inittab ctrlaltdel Nick wrote: I know I've asked about this before on this list, and several of you have repeated the syntax for /etc/inittab, typically: ca:12345:ctrlaltdel:/sbin/shutdown -h now Just looked at mine and it's ca::ctrlaltdel:/sbin/shutdown -h now Perhaps you are not in run levels 1 through 5? Just a thought. Marcy -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Samba process runaway
Samba 2.2.8a in our SLES 8 SP3 systems has a bad bug. Samba keeps running out of control and eating up CPU, meanwhile, customers access to the samba shares dies. When it happens, there appears to be wy too many samba processes spawned, yet only one of them is going bezerk according to top. I've had level 3 samba logging turned on, but I'm not capturing anything that I can identify as the cause. I see some oplock messages, but those come in during good bad times. The other thing I notice is there is typically a file or directory not found error in the log, too, prior to the bad behavior, although I don't see how that could be a cause. Anyone have any ideas as to what might be causing this? Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Monthly forehead bruising: inittab ctrlaltdel
Should doesn't count. How many times have we heard, In theory, practice and theory agree. In reality, theory and practice differ? This is one of those times. :-) Rob van der Heij's warning bout YaST2-sshinstall was probably exactly on target: when I reran the install process today for my test image and made a point of running it, it didn't look familiar to me. I can't believe I missed it, but I apparently I did. Before I had done all that, when I was worrying about why the runlevel was unknown, it didn't matter if I had the 12345 in that insttab line or left it blank; it wasn't getting picked up either way. Forcing the system into run level 3 with an init 3 made it work. Getting a clean re-install seems to have worked wonders. The system now comes up in run level 3, and my acne's even clearing up. I can't decide if I'm relieve to finally get this working or hugely embarrassed that I apparently screwed up the install process so thoroughly. Hopefully, the next time someone has odd-ball issues with run levels and SIGNAL SHUTDOWN, these notes will aim them in the right direction. Nick Hall, Ken (IDS ECCS) wrote: Mine (working) is: ca:12345:ctrlaltdel:/sbin/shutdown -y -g0 Should work either way though. -Original Message- From: Post, Mark K Sent: Tuesday, April 27, 2004 2:14 PM Well, that would only leave 0 and 6 (or unknown as he's reporting), either of which would mean the system wasn't very usable at that moment. :) Mark Post -Original Message- From: Marcy Cortes Sent: Tuesday, April 27, 2004 12:55 AM Perhaps you are not in run levels 1 through 5? Just a thought. Marcy -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
DASD Errors due to R/O
Hello. I am trying to setup a linux/s390 using shared OS DASD using the BIND mountS Guestvol/Basevol procedure. Everything seems to be setup correctly but everytime I boot the R/O system I get this DASD error. This error comes out before the bind mount of /guestvol/etc over /etc and this these error continue non-stop. Anyone know how to tell what this error is? dasd(eckd): We are interested in: CU 3880/00 dasd(eckd): We are interested in: CU 3990/00 dasd(eckd): We are interested in: CU 2105/00 dasd(eckd): We are interested in: CU 9343/00 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: EXAMINE 24: Command Reject detected - fatal error dasd(eckd): Sense data: dasd(eckd):device 0601 on irq 6: I/O status report: dasd(eckd):in req: 0153af00 CS: 0x00 DS: 0x02 dasd(eckd):Failing CCW: 0153afe0 dasd(eckd):Sense(hex) 0- 7: 80 02 00 00 2a 00 00 00 dasd(eckd):Sense(hex) 8-15: 00 00 00 00 00 00 00 14 14:52:15 dasd(eckd):Sense(hex) 16-23: 03 00 05 60 00 68 0f 00 dasd(eckd):Sense(hex) 24-31: 00 00 4c e0 00 00 00 00 dasd(eckd):24 Byte: 0 MSG 0, no MSGb to SYSOP dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: (EXAMINE) ERP chain report for req: 0153af00 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af00: c5c3d2c4 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af10: 0153af00 0153af00 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af20: 01567000 01532f00 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af30: 0153afd0 0302 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af40: ff00 0153afa0 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af50: dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af60: 011e 1a30 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af70: bb221455 8e627242 bb221455 8e627b42 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af80: dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af90: 0004 0030 0055d2b0 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: Channel program (complete): dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153afd0: 63400010 0153afa0 47400010 0153afc0 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153afe0: 85001000 00846000 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153aff0: dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153b000: 0153c000 01539000 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: Failed CCW (0153afe0) already logged end_request: I/O error, dev 5e:05 (dasd), sector 4056 kjournald starting. Commit interval 5 seconds dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: EXAMINE 24: Command Reject detected - fatal error dasd(eckd): Sense data: dasd(eckd):device 0601 on irq 6: I/O status report: dasd(eckd):in req: 0153af00 CS: 0x00 DS: 0x02 dasd(eckd):Failing CCW: 0153afe0 dasd(eckd):Sense(hex) 0- 7: 80 02 00 00 2a 00 00 00 dasd(eckd):Sense(hex) 8-15: 00 00 00 00 00 00 00 14 dasd(eckd):Sense(hex) 16-23: 03 00 05 60 00 68 0f 00 dasd(eckd):Sense(hex) 24-31: 00 00 4c e0 00 00 00 00 dasd(eckd):24 Byte: 0 MSG 0, no MSGb to SYSOP dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: (EXAMINE) ERP chain report for req: 0153af00 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af00: c5c3d2c4 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af10: 0153af00 0153af00 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af20: 01567000 01532f00 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af30: 0153afd0 0302 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af40: ff00 0153afa0 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af50: dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af60: 011e 1a30 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af70: bb221455 8ec75620 bb221455 8ec75f00 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af80: dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153af90: 0004 0030 0055d2b0 dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: Channel program (complete): dasd_erp(3990): /dev/dasdb ( 94: 4),[EMAIL PROTECTED]: 0153afd0: 63400010
Re: DASD Errors due to R/O
On Tue, 2004-04-27 at 14:03, Bob wrote: Hello. I am trying to setup a linux/s390 using shared OS DASD using the BIND mountS Guestvol/Basevol procedure. Everything seems to be setup correctly but everytime I boot the R/O system I get this DASD error. This error comes out before the bind mount of /guestvol/etc over /etc and this these error continue non-stop. Anyone know how to tell what this error is? In the parmfile, specify something like dasd=...,601(ro),... The system is trying to access the r/o device r/w. Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux NFS shares and Windoze interoperability
The ifconfig -a command shows the broadcast address. I am no TCP/IP expert, but I think that your subnet mask must be wrong. This is based on the fact that the 137.70.100.255 broadcast address seems to work. You could try changing the broadcast address on the system that is failing to 137.70.100.255 with ifconfig and see if that works. If it does I would probably change the subnet mask to 255.255.255.0 on all the systems (of course I would test this on one of them first). -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 10:36 AM To: [EMAIL PROTECTED] Subject: Re: Linux NFS shares and Windoze interoperability Of course, now I cant remember how to get linux to barf up the broadcast address it is using, but if memory serves, for all my linuxes, the IP addresses are 137.70.100.xxx and the default gateway is 137.70.100.3, the netmask is set to 255.255.254.0. We orignally had a netmask of 255.255.255.0 but I changed to to ...254.0 per my network group after the install. The broadcast address that was set at install time was, I'm quite sure 137.70.100.255. So what is the implication of changing the netmask after the install? Is that part of what is causing this? Curiously, while doing the'my network places'NFS Nework---add/remove NFS LANs fails, entering the DNS name as \\nokomis in the address bar DOES in fact pull up the NFS shares on that machine and I can navigate them. So that's a plus. Fargusson.Alan [EMAIL PROTECTED] tb.ca.gov To Sent by: Linux on [EMAIL PROTECTED] 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: Linux NFS shares and Windoze interoperability 04/27/2004 10:36 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Your broadcast address looks right to me. I don't know if I can explain this well, but I will try. The subnet mask that you specified says that the subnet has a 9 bit host address. Thus the last 9 bits of the IP address specifies the host on the subnet. The broadcast address on this subnet has the last 9 bits on. In general the broadcast address has all bits of the host part on. Therefore the broadcast address is the upper 23 bits of the IP for the subnet with all ones for the host part, which is 137.70.101.255. The 101 is due to the fact that the last bit is on for the broadcast address. Note that 101 in binary is 01100101 - that last bit is one. A 100 would be 01100100. Now if you are sure that the broadcast address is wrong, then your subnet mask must be wrong. -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 27, 2004 7:48 AM To: [EMAIL PROTECTED] Subject: Re: Linux NFS shares and Windoze interoperability I have been unable to get that to actually see the linux instances on the mainframe. If sees the linux PC in my cube which is also running NFS, and it put that in the 'default lan' group. When I attempt to do the 'add' part it pops up a box saying add/remove NFS LAN's, so I click add. I then get a box that says Add Broadcast Lan (not what I would expect but I go with it) I wants a name to call it, so I put in nokomis. My linux guest running NFS. Then It wants IP address of any Host in the LAN - meaning what exactly? Dunno. I put the IP address of 'nokomis' in there Then it wants the subnet mask, and I enter that. Then it somehow gets the broadcast address by itself, and from what I see it is getting it wrong, as it's on a diff subnet. The IP address of nokimis is 137.70.100.134, and the net mask is 255.255.254.0 but the broadcast address is being returned as 137.70.101.255. As I vaguely recall, the 101 had somethign to do with the VIPA setup on our OSA cards... I am confused here. Steve Gentry Stephen_R_Gentry @LafayetteLife.co To m[EMAIL PROTECTED] Sent by: Linux on cc 390 Port [EMAIL PROTECTED] Subject IST.EDU Re: Linux NFS shares and Windoze interoperability 04/27/2004 09:08 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU James, since you said you installed Unix services, do you have an 'NFS network' entry under 'Entire Network' (under 'My Network Places')? IOW, My Network Places -- Entire Network -- NFS Network. If
Re: Monthly forehead bruising: inittab ctrlaltdel
On the original system, was there a line in inittab similar to the following? # The default runlevel is defined here id:3:initdefault: With no default runlevel, I'm surprised anything was working. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Nick Laflamme Sent: Tuesday, April 27, 2004 2:53 PM To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] Monthly forehead bruising: inittab ctrlaltdel Should doesn't count. How many times have we heard, In theory, practice and theory agree. In reality, theory and practice differ? This is one of those times. :-) Rob van der Heij's warning bout YaST2-sshinstall was probably exactly on target: when I reran the install process today for my test image and made a point of running it, it didn't look familiar to me. I can't believe I missed it, but I apparently I did. Before I had done all that, when I was worrying about why the runlevel was unknown, it didn't matter if I had the 12345 in that insttab line or left it blank; it wasn't getting picked up either way. Forcing the system into run level 3 with an init 3 made it work. Getting a clean re-install seems to have worked wonders. The system now comes up in run level 3, and my acne's even clearing up. I can't decide if I'm relieve to finally get this working or hugely embarrassed that I apparently screwed up the install process so thoroughly. Hopefully, the next time someone has odd-ball issues with run levels and SIGNAL SHUTDOWN, these notes will aim them in the right direction. Nick Hall, Ken (IDS ECCS) wrote: Mine (working) is: ca:12345:ctrlaltdel:/sbin/shutdown -y -g0 Should work either way though. -Original Message- From: Post, Mark K Sent: Tuesday, April 27, 2004 2:14 PM Well, that would only leave 0 and 6 (or unknown as he's reporting), either of which would mean the system wasn't very usable at that moment. :) Mark Post -Original Message- From: Marcy Cortes Sent: Tuesday, April 27, 2004 12:55 AM Perhaps you are not in run levels 1 through 5? Just a thought. Marcy -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 == If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ == -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Samba process runaway
We're running 2.2.8a on several servers and I've never seen this. What we HAVE seen is that if the server loses contact with the LDAP server that contains the user/UID mappings, often the smbd processes hang. I'm not sure if the problem is in smbd, nscd, or nss_ldap. In any case, Windows gives up after 30-60 seconds, and drops the connection. When the workstation tries to reconnect, another smbd process is spawned, and hangs. This continues until the machine fills up with smbd processes. I've seen as many as 1000+ processes with only 80 active users. Normal should be users (as reported by smbstatus) plus 1 or 2. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Wolfe, Gordon W Sent: Tuesday, April 27, 2004 2:47 PM To: [EMAIL PROTECTED] Subject: [LINUX-390] Samba process runaway Samba 2.2.8a in our SLES 8 SP3 systems has a bad bug. Samba keeps running out of control and eating up CPU, meanwhile, customers access to the samba shares dies. When it happens, there appears to be wy too many samba processes spawned, yet only one of them is going bezerk according to top. I've had level 3 samba logging turned on, but I'm not capturing anything that I can identify as the cause. I see some oplock messages, but those come in during good bad times. The other thing I notice is there is typically a file or directory not found error in the log, too, prior to the bad behavior, although I don't see how that could be a cause. Anyone have any ideas as to what might be causing this? Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 == If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ == -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Monthly forehead bruising: inittab ctrlaltdel
Hall, Ken (IDS ECCS) wrote: On the original system, was there a line in inittab similar to the following? # The default runlevel is defined here id:3:initdefault: Yes, that was there. I still ended up in runlevel unknown. With no default runlevel, I'm surprised anything was working. In retrospect, it's not clear what was or wasn't working on that or the other systems on which I probably made the same mistake. The other systems seem able to reach run level 3. Then again, this was the system where I learned how to put fixes on. Maybe I loaded a bad fix, or maybe I applied a patch badly without realizing it. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Samba process runaway
We're not using LDAP, we're using security=server to a Windows 2000 server providing NTLM services... but what you describe sounds close, very close. We keep the virtual host capped at 64 meg ram and 128 meg swap, as it improves performance... I think this keeps us from having thousands of processes, but we definitely get upwards of 50+ extra ones. So what's the cure for this, folks? Local smb.passwd authentication? Our SuSE SLES 7 hosts running Samba samba-2.2.0a-56 don't have this problem. Only the newer SLES 8 (service pack 3). Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Hall, Ken (IDS ECCS) Reply To: Linux on 390 Port Sent: Tuesday, April 27, 2004 12:23 PM To: [EMAIL PROTECTED] Subject: Re: Samba process runaway We're running 2.2.8a on several servers and I've never seen this. What we HAVE seen is that if the server loses contact with the LDAP server that contains the user/UID mappings, often the smbd processes hang. I'm not sure if the problem is in smbd, nscd, or nss_ldap. In any case, Windows gives up after 30-60 seconds, and drops the connection. When the workstation tries to reconnect, another smbd process is spawned, and hangs. This continues until the machine fills up with smbd processes. I've seen as many as 1000+ processes with only 80 active users. Normal should be users (as reported by smbstatus) plus 1 or 2. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Wolfe, Gordon W Sent: Tuesday, April 27, 2004 2:47 PM To: [EMAIL PROTECTED] Subject: [LINUX-390] Samba process runaway Samba 2.2.8a in our SLES 8 SP3 systems has a bad bug. Samba keeps running out of control and eating up CPU, meanwhile, customers access to the samba shares dies. When it happens, there appears to be wy too many samba processes spawned, yet only one of them is going bezerk according to top. I've had level 3 samba logging turned on, but I'm not capturing anything that I can identify as the cause. I see some oplock messages, but those come in during good bad times. The other thing I notice is there is typically a file or directory not found error in the log, too, prior to the bad behavior, although I don't see how that could be a cause. Anyone have any ideas as to what might be causing this? Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 == If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ == -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Samba process runaway
out of control and eating up CPU, meanwhile, customers access to the samba shares dies. When it happens, there appears to be wy too many samba processes spawned, yet only one of them is going bezerk according to top. The parent smbd forks one smbd for each connection. So each client (including WINS servers in the domain) should get a smbd. Are there more smbd's than that? smbstatus will show you how many connected users there are at any time, assuming your connections.tdb file is ok. Everyone's access dies, or just the one that belongs to the looping smbd? You might want to attach strace or ltrace or gdb to the pid that's using all your CPU to get a handle on where it's stuck. I've had level 3 samba logging turned on, but I'm not capturing anything that I can identify as the cause. I see some oplock messages, but those come in during good bad times. The other thing I notice is there is typically a file or directory not found error in the log, too, prior to the bad behavior, although I don't see how that could be a cause. Which file not found? Is this same message present in good times and bad, or only in bad? ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Samba process runaway
Everyone's access dies once memory is full, which doesn't take long in 64mRam/128mSwap. The samba process running away is owned by root, while the users samba processes have just quietly stopped working but still exist. The samba processes are outnumbering users in the extreme. ~13 active users this morning and 67 samba processes were running. Only two people had locked files. The extra samba processes are all owned by root. I haven't done the strace because of our charging/billing structure. The file not found error appears every once in a while under normal conditions, but there are several in a row before the madness begins. We had experimented with a daily recycle of samba via cron in hopes of introducing stability, but this did not help. There is no pattern for when this is occuring time wise, so we never know when it will hit. It can go weeks without a problem, then 1 - 3 hits in two days. Frustrating, to say the least. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Daniel Jarboe Reply To: Linux on 390 Port Sent: Tuesday, April 27, 2004 1:09 PM To: [EMAIL PROTECTED] Subject: Re: Samba process runaway out of control and eating up CPU, meanwhile, customers access to the samba shares dies. When it happens, there appears to be wy too many samba processes spawned, yet only one of them is going bezerk according to top. The parent smbd forks one smbd for each connection. So each client (including WINS servers in the domain) should get a smbd. Are there more smbd's than that? smbstatus will show you how many connected users there are at any time, assuming your connections.tdb file is ok. Everyone's access dies, or just the one that belongs to the looping smbd? You might want to attach strace or ltrace or gdb to the pid that's using all your CPU to get a handle on where it's stuck. I've had level 3 samba logging turned on, but I'm not capturing anything that I can identify as the cause. I see some oplock messages, but those come in during good bad times. The other thing I notice is there is typically a file or directory not found error in the log, too, prior to the bad behavior, although I don't see how that could be a cause. Which file not found? Is this same message present in good times and bad, or only in bad? ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Samba process runaway
Rather than use strace can you look at /proc/pid/status and check the registers/psw and then check it against /proc/pid/maps to find out where in the app it is. Then you can get the offset within the library (presumably) and match that against an nm of that library to find the routine it is in. Unfortunately, they'll probably be in wait or something equally as useless but you may strike it lucky. -Original Message- Everyone's access dies once memory is full, which doesn't take long in 64mRam/128mSwap. The samba process running away is owned by root, while the users samba processes have just quietly stopped working but still exist. The samba processes are outnumbering users in the extreme. ~13 active users this morning and 67 samba processes were running. Only two people had locked files. The extra samba processes are all owned by root. I haven't done the strace because of our charging/billing structure. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
acf2/vm
Has anyone on the list recent experience with using acf2/vm to secure vm? Best Regards, Joe -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
term zLinux copyrighted by whom?
The official Big Blue legal position on the term zLinux is that it is copyrighted by another company and one should use the terms Linux for zSeries or Linux for s/390. Anyone know who the other company is? = Jim Sibley RHCT, Implementor of Linux on zSeries Computer are useless.They can only give answers. Pablo Picasso __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: term zLinux copyrighted by whom?
Turbolinux Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jim Sibley Sent: Tuesday, April 27, 2004 6:09 PM To: [EMAIL PROTECTED] Subject: term zLinux copyrighted by whom? The official Big Blue legal position on the term zLinux is that it is copyrighted by another company and one should use the terms Linux for zSeries or Linux for s/390. Anyone know who the other company is? = Jim Sibley RHCT, Implementor of Linux on zSeries Computer are useless.They can only give answers. Pablo Picasso __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
RES: acf2/vm
I installed and give maint on 2 different VM/VSE sites till 0ne year ago. One use VM (for access control) and CICS (for transaction security) Other only for Multi-session (TPX) access under VM Carlos Alberto Bodra VM/VSE Consultant Sao Paulo - Brazil -Mensagem original- De: Linux on 390 Port [mailto:[EMAIL PROTECTED] Em nome de Joseph Beiter Enviada em: terça-feira, 27 de abril de 2004 18:18 Para: [EMAIL PROTECTED] Assunto: acf2/vm Has anyone on the list recent experience with using acf2/vm to secure vm? Best Regards, Joe -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 Esta mensagem foi verificada pelo E-mail Protegido Terra. Scan engine: VirusScan / Atualizado em 26/04/2004 / Versco: 1.5.2 Proteja o seu e-mail Terra: http://www.emailprotegido.terra.com.br/ E-mail classificado pelo Identificador de Spam Inteligente Terra. Para alterar a categoria classificada, visite http://www.terra.com.br/centralunificada/emailprotegido/imail/imail.cgi?+_u= cbodra_l=1083100840.571814.31966.gravatal.terra.com.br -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: acf2/vm
Have your local sales team get you the current information for eTrust CA-ACF2 for z/VM. They should also be able to get you reference sites that you can talk with. There is a new release going beta with a number of new features including the pswd controls that exist in the z/OS version, PAM support to authenticate the Linux/390 logons, etc. Thank you, Mitchell Rozonkiewiecz Development Manager Computer Associates Int'l, Inc. 2400 Cabot Drive Wing 2C Lisle, IL 60532 630-505-6804 - Phone 630-505-1222 - Fax [EMAIL PROTECTED] - Email http://ca.com/caworld/ -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Joseph Beiter Sent: Tuesday, April 27, 2004 4:18 PM To: [EMAIL PROTECTED] Subject: acf2/vm Has anyone on the list recent experience with using acf2/vm to secure vm? Best Regards, Joe -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
