Re: LVMs gone!
On Tue, Jun 8, 2010 at 11:10 AM, Macioce, Larry larry.maci...@com.state.oh.us wrote: I tried to reboot the test system today and it sits in init 1 , NONE of the lvgs can be accessed. When a reboot occurs, Linux doesn't see volume 207(this was the vol used to increase the filsesystem) Looked at user direct and the volume(207) is there. When we looked at Linux, it showed offline but there. We can bring it online but it fails through a reboot...du It sounds like you may just need the device to be configured online at boot time. This might be adding 207 into your dasd= range in zipl.conf, or for SLES 9 I think you rerun your mkinitrd/zipl scripts with the device online. Is there a way once online to restart the other services ? telinit 3 (or whichever runlevel is appropriate for your environment). Good luck, ~ Daniel -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Change SAMBA password
While it's beyond what you were asking for, here's another vote for Samba running in SECURITY=DOMAIN mode with winbind if your users are already authenticating in a Windows Domain / Active Directory type environment. Word of warning: it is another layer of complexity and relinquishment of control which can cause some surpises. For example, our Windows server team recently broke us when they upgraded the Domain Controllers to Windows Server 2008 R2 (our permanent fix was to upgrade the Samba version). That said, running with winbind is great for end-users and Single Sign On (if your end-users are on Windows clients authenticating against a domain, everything just works). ~ Daniel -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
Posting on Linux-390 list too... --- In hercules-...@yahoogroups.com, Harold Grovesteen h.grovst...@... wrote: The assumption that has been made is that the files listed in your .ins file were in fact loaded. That assumption needs to be validated. Please display real storage for each of the starting addresses in your .ins file. This should validate that what you think got loaded did get loaded. The command format is: r hexaddr.len So: r .1F will display the first 32 bytes of storage. If what is displayed is other than 0x00 then something did in fact get loaded. r 0001040C.4 etc. Thanks for thinking of that suggestion. Based on the response on the Linux-390 Marist list, I pulled from SVN last night: 5323. Incidentally, the make blew up in po; I had to ./configure --disable-nls. Now, doing the displays like you mentioned in that build... # Start up Hercules (storage is empty): HHCAO001I Hercules Automatic Operator thread started; tid=76FA7B90, pri=0, pid=11594 r 0.1f R::K:00= R:0010:K:00= # IPL the SLES11 .ins and get the disabled wait state; storage is no longer empty: ipl ./rdr/sles11/suse.ins HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A r 0.1f R::K:06=0008 8298 0218 6050 ...q-.. R:0010:K:06=0268 6050 40404040 40404040 -.. r 1040c.f R:0001040C:K:06=0080 00C4CC37 .D.. r 10414.f R:00010414:K:06=00C4CC37 .D.. r 80.1f R:0080:K:06=1F8B0808 5C47B449 0203696E 69747264 *.. R:00800010:K:06=00AC590B 7C935596 BF5F9A36 01298452 @l.o.^d. r 10480.1f R:00010480:K:06=72616D64 69736B5F 73697A65 3D363535 ./_...,^..:. R:00010490:K:06=33362072 6F6F743D 2F646576 2F72616D ??/_ # The files specified in the .ins files do appear to be loaded. For comparisons sake I loaded the SLES10SP2 vmrdr.ikr to see if it looked the same... loadcore ./rdr/sles10SP2/vmrdr.ikr HHCPN112I Loading ./rdr/sles10SP2/vmrdr.ikr to location 0 HHCPN113I 7161160 bytes read from ./rdr/sles10SP2/vmrdr.ikr r 0.1f R::K:06=0008 8298 0218 6050 ...q-.. R:0010:K:06=0268 6050 40404040 40404040 -.. # Both start off the same. I checked outside of Hercules and the first 671 bytes of the files are identical. For grins restart with the SLES10SP2 vmrdr.ikr and SLES11 initrd/parmfile/etc. restart HHCPN038I Restart key depressed CPU: SIGP Set architecture mode (12) CPU, PARM 0001: CC 0 HHCCP007I CPU architecture mode set to z/Arch HHCCP014I CPU: Addressing exception CODE=0005 ILC=6 PSW=1001 8000 00011176 INST=E5015000 TPROT 0(5),0(0) test_protection R:4000: Translation exception 0005 R::K:06=0008 8298 000A ...q R0=00728F04 R1=0002 R2= R3=006DC610 R4= R5=4000 R6= R7= R8= R9=4000 RA=0010 RB= RC=00010400 RD=00011002 RE=00011058 RF=0069FF60 HHCCP014I CPU: Special-operation exception CODE=0013 ILC=6 PSW=1001 8000 00011290 INST=C800 MVCOS 0(0),0(0),0move_with_optional_specifications R::K:06=0008 8298 000A ...q R::K:06=0008 8298 000A ...q R0= R1=00011290 R2= R3=006DC628 R4=4002 R5=4002 R6= R7= R8=0001 R9=4000 RA=000F RB= RC=006DC5F8 RD=00011002 RE=00011058 RF=0069FF60 HHCCP014I CPU: Operation exception CODE=0001 ILC=4 PSW=1001 8000 000112AE INST=B9AF0011 PFMF 1,1perform_frame_management_function R:: Translation exception 0005 R:: Translation exception 0005 R0= R1= R2= R3=006DC628 R4=4002 R5=4002 R6= R7= R8=0001 R9=4000 RA=000F RB= RC=006DC5F8 RD=00011002 RE=00011058 RF=0069FF60 HHCCP014I CPU: Operation exception CODE=0001 ILC=4 PSW=0001 8000 000112CC INST=B9AB0001 ? , ? R::K:06=0008 8298 000A ...q R::K:06=0008 8298 000A ...q R0= R1=
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
I'm pretty sure that's by design, and not a problem. The kernel starts out in 31-bit mode, and then switches to 64-bit mode. I've been seeing the same thing for years now, and I still do on my own Hercules setup that can successfully boot up SLES11. Hi Mark, can you confirm? $ md5sum vmrdr.ikr 98573dfb90ece6c6deaaf936e7d7e725 vmrdr.ikr Also, what release of hercules? I might as well try that too for completeness sake. Thanks, ~ Daniel -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
What kind of hardware and operating system are you running this on? A Ubuntu 8.10 installation. P4 Intel chip, 1GB RAM. I still end up at disabled wait state with 3.04.1 (though with the older release of hercules it reports instcount of 18 rather than 2). I'll have to try this on some other boxes. herc 3.04.1 SLES11 IPL from suse.ins: HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A Command == CPU PSW=000A M.W. instcount=18 herc 3.04.1 SLES10SP2 IPL from suse.ins: IPLs, but ultimately blows up with an instruction count of about 1.7 million (before installer asks for anything) herc 3.04.1 Debian Lenny IPL from reader: IPLs, installer runs but is unable to activate dasd herc 3.06 SLES11 IPL from suse.ins: HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A Command == CPU PSW=000A 24M.W. instcount=2 herc 3.06 SLES10SP2 IPL from suse.ins: IPLs, full installation complete without apparent problem herc 3.06 Debian Lenny IPL from reader: IPLs, full installation complete without apparent problem -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
On Tue, Apr 14, 2009 at 3:34 PM, Neale Ferguson wrote: Can you display the program old PSW and the instruction that the address portion of the PSW points to? (Actually, the address less the ILC.) That fished it out. Enabling instruction stepping increased the instruction count, but not by much. s+ HHCPN040I Instruction stepping on ipl ./rdr/sles11/suse.ins HHCCP007I CPU architecture mode set to ESA/390 PSW=0008 8298 INST=481000B8 LH1,184(0,0) load_halfword R:00B8:K:06=02000500 6050 02000550 6050 -.-.. GR00= GR01= GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 829C INST=461003F0 BCT 1,1008(0,0) branch_on_count R:03F0:K:06=581003FE 07F100B1 E7B80001 0401 .1..X... GR00= GR01=0200 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 83F0 INST=581003FE L 1,1022(0,0)load R:03FE:K:06=0001 0060 3F90C3C8 C1D5C7C5 40D9 .-..CHANGE R GR00= GR01=01FF GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 83F4 INST=07F1 BCR 15,1 branch_on_condition_register GR00= GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 8001 INST=0DD0 BASR 13,0 branch_and_save_register GR00= GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13= GR14= GR15= PSW=0008 80010002 INST=B2020D80 STIDP 3456(0) store_cpu_id R:0D80:K:04= GR00= GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= CR00=00E0 CR01= CR02= CR03= CR04= CR05= CR06= CR07= CR08= CR09= CR10= CR11= CR12= CR13= CR14=C200 CR15= PSW=0008 80010006 INST=A7080001 LHI 0,1 load_halfword_immediate GR00= GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= PSW=0008 8001000A INST=4110D026 LA1,38(0,13) load_address R:00010028:K:06=96724110 1002A706 FFF058D0 D03847F0 o.x..0.}}..0 GR00=0001 GR01=0001 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= PSW=0008 8001000E INST=D5010D841000 CLC 3460(2,0),0(1) compare_logical_character R:0D84:K:06=9672 o... R:00010028:K:06=96724110 1002A706 FFF058D0 D03847F0 o.x..0.}}..0 GR00=0001 GR01=00010028 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= PSW=0008 80010014 INST=A774000B BRC 7,*+22 branch_relative_on_condition GR00=0001 GR01=00010028 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= PSW=0008 80010018 INST=8200D01E LPSW 30(13) load_program_status_word R:00010020:K:06=000A 96724110 1002A706 o.x. GR00=0001 GR01=00010028 GR02= GR03= GR04= GR05= GR06= GR07= GR08= GR09= GR10= GR11= GR12= GR13=80010002 GR14= GR15= HHCCP043I Wait state PSW loaded: PSW=000A HHCCP011I CPU: Disabled wait state PSW=000A SLES11 was checking the CPU Model, not liking 9672, and aborting. I changed CPUMODEL to something more current (2096) and the SLES11 installer IPLed without incident. Thank you everybody for the eyes and the
IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
I'm having trouble IPLing the starter SLES11 system using Hercules 3.06. The IPL method should be equivalent to a LPAR load from CD-ROM. The deployment.pdf included within SuSE's docu directory didn't reveal any obvious differences why what works for SLES10 SP2 installation under Hercules doesn't work for me now with SLES11 media. ipl /path/to/suse.ins now results in: HHCCP007I CPU architecture mode set to ESA/390 HHCCP011I CPU: Disabled wait state PSW=000A Command == CPU PSW=000A 24M.W. instcount=2 The new SLES11 suse.ins is: * SuSE Linux for zSeries Installation/Rescue System vmrdr.ikr 0x initrd.off 0x0001040c initrd.siz 0x00010414 initrd 0x0080 parmfile 0x00010480 All files are present. For reference, the SLES10SP2 suse.ins was fairly similar and works without problems for SLES10: * SuSE Linux for zSeries Installation/Rescue System vmrdr.ikr 0x initrd.siz 0x00010414 initrd 0x0080 parmfile 0x00010480 There's no z/VM in the mix. I also replaced vmrdr.ikr with cd.ikr in the .ins file, but the result was the same. Has anyone already been through a SLES11 LPAR IPL from CD, or can get me started in the right direction on this? Thanks, ~ Daniel -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IPL of SLES11 .ins file in Hercules yields immediate disabled wait state
I would not deny that this might be a problem, but with an instruction count of 2, it did not get very far, unless of course it is the very first instruction. This question came up on the Hercules list, and I recommended this list. Can anyone validate for the poster, the correct .ins file content? I ran into a bug earlier when using the 3.0.5 .deb package that made dasd activation fail. I had already gotten past that one by downloading the hercules 3.0.6 release and building that. I figured it wouldn't hurt to pull the latest from SVN for grins when I get home and give it a whirl *just in case*. The initrd looks perfectly valid: a gzipped cpio archive. I'm not sure how to validate the different .ikr files at this point. According to file the headers indicate both SLES10SP2 and SLES11 are Applesoft BASIC program data. I have some reading to do here. The instruction count of two gave me hope that it was something silly with a quick solution, but I will dig more. I IPLed the debian Lenny installer from the reader so it's not really an apples to apples, but SLES 10 SP2 was an ipl suse.ins which is the same method I'm trying to use with SLES 11. Thanks, ~ Daniel -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Upgrade to SLES10 (s390x from s390)
It used to be the case that there was not a supported upgrade path from SLES 31-bit to 64-bit addressing modes. Is that still the case? Has anyone performed a SLES9 SP3 s390 - SLES10 s390x upgrade in place, or is trying this still more trouble than its worth (i.e. install clean and be done with it)? We have no SLES10 yet, just planning ahead. The most descriptive thing I can find right now is: http://www.novell.com/documentation/sles10/index.html?page=/documentatio n/sles10/sles_admin/data/cha_upgrade.html, which says nothing about going from one addressing mode to the other. Thanks, ~ Daniel -- 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: SUSE Linux for 390
I actually don't think there is any software checking. We bought support during the period and we never had to change anything from the original install. What ends is your ability to pull maintenance from portal. ~ Daniel -- 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: Large Mail file and Warn file
Thanks, Would you be willing to send a listing of your logrotate.config file?. /etc/logrotate.d/syslog is installed with your syslog package Just make sure you have logrotate installed and set up in cron (normally this is done automatically for you, run daily). ~ Daniel -- 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: Can't Access YAST to complete install
You can also ^C out of the install script at the console and eventually it will drop you into a shell. Next time you re-ipl, it will pick up in the install script again. Once in a shell check the output of /sbin/route. Make sure you can ping -c 1 ip_of_your_default_gateway, that kind of thing (don't forget the -c 1). Your gateway will probably be 155.180.147.33 if it's the first host address of the subnet. I presume you can ping your SLES8 image, and it's in the same subnet? ~ Daniel -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Friday, August 12, 2005 3:43 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Can't Access YAST to complete install Everything looks good from the log. The OSA driver loads and the interface gets configured. Is the /28 subnet mask correct for your system? That equates to 255.255.255.240. What system are you pinging from? Is it on the same subnet (Guest LAN?) If not, are there any firewalls in between that might be dropping icmp packets? You might just try re-IPLing from 200 and see if it goes away (without doing a complete reinstall just yet), because it might just be a glitch. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, August 11, 2005 9:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Can't Access YAST to complete install Hello All, I'm working on installing SLES9 with SP2 on z/VM 4.4 and have trouble after the reboot. I'm installing from a NFS server and access all the media fine. OSA Express attached and using MPROUTE in VM for OSPF. I currently have SLES8 up in this environment without problems. I go through the initial IPL from the RDR Enter all the IP and NFS info then successfully connect via VNC to do the install in YAST Dasd formats fine. (Virt Device is 0x0200 3390-3 ) Partitions without error I select minimal install and set the TZ and set run level to 3 Install completes without error system reboots, I IPL 200 and SUSE begins to load, gets to the point that it says to reconnect to VNC. UNABLE to connect to VNC, Can not ping the IP of the guest. below is the log as it starting after the install to begin the customization step 00: IPL 200 00: Booting default (ipl)... Linux version 2.6.5-7.191-s390 ([EMAIL PROTECTED]) (gcc version 3.3.3 (SuSE Linux) ) #1 SMP Tue Jun 28 14:58:56 UTC 2005 We are running under VM (31 bit mode) This machine has an IEEE fpu On node 0 totalpages: 262144 DMA zone: 262144 pages, LIFO batch:31 Normal zone: 0 pages, LIFO batch:1 HighMem zone: 0 pages, LIFO batch:1 Built 1 zonelists Kernel command line: root=/dev/dasda1 selinux=0 TERM=dumb elevator=cfq BOOT_IMAGE=0 PID hash table entries: 4096 (order 12: 32768 bytes) CKRM Initialization .. Initializing ClassTypetaskclass .. Initializing ClassTypesocketclass CKRM Initialization done Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes) Inode-cache hash table entries: 131072 (order: 7, 524288 bytes) Memory: 1029632k/1048576k available (3255k kernel code, 0k reserved, k data, 100k init) Security Scaffold v1.0.0 initialized SELinux: Disabled at boot. Mount-cache hash table entries: 512 (order: 0, 4096 bytes) Detected 2 CPU's Boot cpu address 0 cpu 0 phys_idx=0 vers=FF ident=0F32CD machine=2084 unused=8000 cpu 1 phys_idx=1 vers=FF ident=0F32CD machine=2084 unused=8000 Brought up 2 CPUs checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 1559k freed khelper: max 64 concurrent processes debug: Initialization complete resid is -1 name is io NULL CKRM .. create res clsobj for resouce ioclass taskclass par= NET: Registered protocol family 16 VFS: Disk quotas dquot_6.5.1 Initializing Cryptographic API RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize loop: loaded (max 8 devices) md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 Channel measurement facility using extended format (autodetected) NET: Registered protocol family 2 IP: routing cache hash table of 8192 buckets, 64Kbytes TCP established hash table entries: 262144 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 262144 bind 65536) NET: Registered protocol family 1 resid is -1 name is cpu NULL CKRM .. create res clsobj for resouce cpuclass taskclass par= init_ckrm_sched_res , resid= 5 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem). Starting udev Creating devices Loading kernel/fs/jbd/jbd.ko Loading kernel/fs/ext3/ext3.ko Loading kernel/drivers/s390/block/dasd_mod.ko Loading kernel/drivers/s390/block/dasd_eckd_mod.ko Loading kernel/drivers/s390/block/dasd_fba_mod.ko Activating DASDs: 0.0.0200:0Configuring device 0.0.0200 Setting device online dasd(eckd):
Re: SLES9 service packs 1 and 2
The information can be found under CORE of your release on portal. Details: s390: http://portal.suse.com/psdb/d217ab2113221d24870fee955dc766cf.html s390x: http://portal.suse.com/psdb/ad5d207a398847172fbd448b7fc0b61d.html Long story short: http://sdb.suse.de/download/s390/update/SUSE-CORE/9/images/ http://sdb.suse.de/download/s390x/update/SUSE-CORE/9/images/ portal login/password required of course, ~ Daniel -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ann (ISD, IT) Sent: Tuesday, July 19, 2005 10:59 AM To: LINUX-390@VM.MARIST.EDU Subject: SLES9 service packs 1 and 2 How are folks getting service pack 2 for SLES9 ? I can only find SP1 from the Novell customer care portal. Are you getting it from a SuSE site? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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: apt-get dist-upgrade abended!
So what's happening? Do you have a half configured package, and dpkg attempts to finish the configuration and fails? Does a dpkg --configure -a tell you anything interesting? ~ Daniel -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Wicks Sent: Wednesday, June 22, 2005 4:26 PM To: LINUX-390@VM.MARIST.EDU Subject: apt-get dist-upgrade abended! Greetings; I started to upgrade Debian and everything was going along fine when it tried to install and activate Appletalk or some such thing and couldn't do it. So, it just quit! Seems to be an , shall we say inconvenient thing to do! That doesn't sound like a terminal error to me! But the immediate problem is I can't figure out how to restart it, re-do it, undo it, or anyting else! Anybody know what the recovery procedures are in this situation? Many TIA! Dennis -- Dennis G. Wicks Systems Programmer [EMAIL PROTECTED] Communications Data Group Tel: (217)355-7117 Fax: (217)351-6994 102 S. Duncan Rd. Champaign, IL 61822 -- 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: apt-get dist-upgrade abended!
Thanks for the reply! Nothing is happening! Every thing I have tried with apt-get just returns 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. So not sure where the problem is yet... you try to apt-get install a new package and you get no messages except 0 upgraded, 0 newly installed... etc? If there's nothing to do you'll see that message, but usually beforehand it'll tell you the package is already installed at the current version. You might want to try your apt-get with -o Debug::pkgProblemResolver=yes to see if that tells you anything more. -- 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: apt-get dist-upgrade abended!
[bromine:/]$ apt-get -o Debug::pkgProblemResolver=yes dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Starting Starting 2 Done Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [bromine:/]$ There's nothing for apt to do. It's already performed the upgrade to its satisfaction. ~ Daniel -- 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: apt-get dist-upgrade abended!
That is exactly the problem. It hasn't finished at all! Isn't there some way to force it to restart? Or do I just use the MicroSoft default solution of reformat and reinstall? You still haven't said what's not working... just that you saw something that might have been an error message possibly related to installing or activating appletalk, and you fear that your apt-get dist-upgrade failed. Usually if an apt upgrade dies, dpkg will have pending packages to install/configure. Your dpkg doesn't. Barring any more specifics on this appletalk message... since dpkg and apt seem 100% happy, the most rational conclusion is they've completed successfully. ~ Daniel -- 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: Install problem again
I can´t get by the initrd 75% problem when installing. Is this for x86? Was a little confused at all the i386 talk in your email. Otherwise, this sounds similar to an experience we recently had. When using either the SLES9 or SLES9-SP1 installation images the process would hang with zipl (would stall at 75% on the progress bar). This problem was z/VM related. Sometime earlier in the install process pdflush would die with an illegal operation in do_writepages (calltrace was printed to the z/VM guest's console). One workaround might be to turn off all linux swap during the install (and run the install with at least 512MB storage). At IBM's recommendation we switched the root installation filesystem from cramfs to ext2 (replacing sles9/CD1/boot/root and increasing the ramdisk size appropriately in sles9/CD1/boot/parmfile). If this sounds like the same situation and disabling swap doesn't help you, you can email me offlist for instructions to create the ext2 root. Or if it hasn't been removed yet you might still be able to wget ftp://testcase.boulder.ibm.com/linux/fromibm/24487/root.ext2 and save yourself some time. This fs created for the SLES9 GA installation process. The new parmfile should read: ramdisk_size=196608 root=/dev/ram1 ro init=/linuxrc TERM=dumb ~ Daniel -- 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 questions
1. Can SAMBA handle nested global groups? I don't believe so - UNIX/Linux groups cannot contain groups. I recall someone flattened nested groups somehow, but this was a migration strategy, not a coexistence one. Support for nested groups in Samba3 is fairly new. Mind link wrap... http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetCommand.ht ml#id2563921 It should also work with usrmgr in windows. I don't use them myself so can't say how well they work, but I remember something about it working with Samba tdb backend and being broken with ldap backend. 2. Are there reference sites and/or other IBM experience with SAMBA and Active Directory? I know there are a few shops out there doing this. I recall TCS presented on Samba at SHARE about a year ago. Anyone? All part of NT domain, no AD yet. ~ Daniel -- 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: z/VM Operator Console
We noticed that when we IPL the z/VM system, the operator console does not go into scroll more right away. It starts in ?VM READ? and sits there with the ?more? prompt until the 60 second timeout and scrolls the next screen. After the IPL is completed and once we hit enter, it will go into ?running? and start to scroll. That's probably because it hasn't run the profile at that point... right? Another enter at the first VM READ will run your profile exec on 191 (A) ~ Daniel -- 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
mainframe time for developement?
Is anyone aware of any sources that provide mainframe time for porting linux applications to s390 and zSeries hardware? I seem to remember some kind of IBM community, and perhaps something offered by sourceforge, but looking at both now and through this lists archives I can't find any information. Thanks, ~ Daniel -- 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: OT: password rules, was: pam_cracklib.so questions
Yeah, good luck making this stick. You *KNOW* the CEO's password is boobies. And change the combination on my luggage! (spaceballs) -- 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 V3 on zSeries Redpiece
In conclusions and recommendations, Our optimal configuration included: 1 MB of Memory ...? ~ Daniel -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ferguson, Neale Sent: Monday, March 21, 2005 8:46 AM To: LINUX-390@VM.MARIST.EDU Subject: Samba V3 on zSeries Redpiece See: http://www.redbooks.ibm.com/redpieces/pdfs/redp3988.pdf This document provides the reader with basic performance rules of thumb for Samba Version 3.0.5 on zSeries Linux and gives background information that can be used in configuring and tuning your Samba V3 environment. The data was developed using an IBM internal workload generator to simulate a heavy transaction load. It identifies the parameters for optimum performance of Samba V3. -- 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: dasd/initrd question for 2.6
SLES9 uses 3 sources for activating dasds. If I recall correctly SLES9 activates the dasds in this order: 1. entries in zipl.conf (dasd=) (dynamically activated by code in the initrd) 2. dasds which were active when mkinitrd was executed. (And exactly in the same order) (These are hardcoded in your initrd) 3. dasds defined in /etc/sysconfig/hardware/ Thanks everyone for clarifying. The problem I bumped into was that the (And exactly in the same order) part of number 2 is not true beyond 26 dasd devices with the /sbin/mkinitrd that is provided with the mkinitrd-1.0-199.53 rpm (in my case the culprit was on line 22 for dir in /sys/block/*; do instead of something like for dir in /sys/block/dasd? /sys/block/dasda?; do in the s390_dasd_sysfs() procedure. Glad to learn that #1 is always a failsafe :). ~ Daniel -- 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/initrd question for 2.6
In our 2.4 systems we set the dasd device order with zipl.conf. The order the devices were added corresponded to which minor number it received... /dev/dasda before /dev/dasdb, etc. Now our SLES9 system uses the initrd... In the initrd's linuxrc script, there are a bunch of calls like: echo -n 0.0.0500:0 /sbin/dasd_configure 0.0.0500 1 0 echo -n 0.0.3010:0 /sbin/dasd_configure 0.0.3010 1 0 echo -n 0.0.3011:0 /sbin/dasd_configure 0.0.3011 1 0 /sbin/dasd_configure sets the device online etc... Does the order they are listed in the initrd's linuxrc script correlate to /dev/dasda, /dev/dasdb, etc... or is which device gets which minor number determined by some other mechanism? The reason I ask is we were trying out yast for SLES9, added some new devices online and did the parallel format (spiffy)... but before quitting and having YaST update its configuration files, we went into LVM management. Here YaST ended up hanging and the process was killed. I manually ran mkinitrd and zipl, but I am concerned with dasd ordering now, and wonder if I need to fix this. /proc/dasd/devices currently shows: 0.0.0500(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 27000 blocks, 105 MB 0.0.1000(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 300420 blocks, 1173 MB 0.0.2000(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 63000 blocks, 246 MB 0.0.2001(ECKD) at ( 94:12) is dasdd : active at blocksize: 4096, 18000 blocks, 70 MB etc And since our fstab is device name based instead of label based I am concerned with the mkinitrd ordering until I know better... Thanks for any info, ~ Daniel -- 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
SLES9 mkinitrd problem? (was: dasd/initrd question for 2.6)
mkinitrd appears to add the dasd devices as they appear in alphabetical order of /sys/block. Which means dasda, dasdaa, dasdab, dasdac, dasda* before dasdb, dasdc, etc. Is anyone else using SLES9 that, after install time, added more devices to put you over 26? Thanks, ~ Daniel -- 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 and Apache Crash System
Current: Kernel: 2.4.9-17. Samba: 2.2.8a, Apache: 1.3.22. You should try a newer RH 7.2 s390 kernel. The 2.4.9-17 kernel for RH 7.2 s390 had a weird interaction with samba. ~ Daniel -- 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: Character mode text editor
It depends on the sed... For example, an update in place from Unix style end of lines to the Windows carriage return style for some files. sed -i 's/$/\r/' filename works on sles9 and fedora core 3, but not sles8 ~ Daniel -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: Wednesday, January 19, 2005 1:49 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Character mode text editor I don't believe that sed will do an in-place edit. Hence you must pipe the output to another file. All the Best Mark Perry -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Fargusson.Alan Sent: Wednesday, January 19, 2005 5:27 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Character mode text editor For this it would seem that sed would be a little lighter. Off the top of my head: sed s/fred/joe/g I didn't test this. You may need a -e or something. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Mark Perry Sent: Wednesday, January 19, 2005 2:18 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Character mode text editor On the very few occasions that I have made a mistake to an /etc ASCII boot file (ok more than a few times), I have used Perl from the command line to make simple changes and hence avoid a true editor. If you use the -i option it even makes a backup for you, plus it can update multiple files in one pass. Example to change the string fred to joe (what you expected foobar?) in all files beginning start in the current subdirectory try the following: perl -p -ibackup -e's/fred/joe' start* I would suggest that you experiment with non critical files first ;-) All the Best Mark Perry -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Seader, Cameron Sent: Tuesday, January 18, 2005 10:36 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Character mode text editor vi does not work on a vm console when you are logged onto linux from there. -- 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 -- 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 3.0
Many of them are the same type of printer HPLaserJet 4si, HPLaserJet 5, etc. and distributed to over 150 drops/locations through-out our campus. During the process of setting up these printers using Point-and-Print I have scripted several steps to save time. But I have not been able to script the command(s) used to associate a printer with its print driver. I have researched the rundll32 printui command and all of my attempts to execute it and associate a printer with a particular print driver fails. I know that the command has to be passed onto Linux and run, and I was thinking I could execute that command directly in Linux. Does anyone have any experience in this area? Which steps have you scripted? The rpcclient command to associate a printer share with a driver is setprinter share-name driver-name ~ Daniel -- 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: Problems using SIGNAL SHUTDOWN
1. Test : zipl.conf without vmpoff=LOGOFF shell command poweroff does not work for both, VM recognizes shutdown of GUEST2, but no logoff 2. Test : zipl.conf with vmpoff=LOGOFF shell command poweroff works for both, VM recognizes shutdown of GUEST2, but no logoff The guest were running disconnected all their lifetime ... Any help still appreciated ... Catching up on mail and didn't see a resolution here yet. Since you're grasping at straws at this point I hope you don't mind me asking... you are writing the ipl text with zipl after modifying zipl.conf, right? ~ Daniel -- 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 equivalents of Unix commands?
A pseudo-equivalent to prstat is top, but top lacks prstat's granularity. Pstack was ported to linux and is available in at least Debian's and RedHat's repositories (maybe others), though I don't see anything for SuSE. A Fedora srpm is here: http://download.fedora.redhat.com/pub/fedora/linux/core/development/SRPM S/pstack-1.2-4.src.rpm HTH, ~ Daniel -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of James Melin Sent: Friday, December 10, 2004 10:41 AM To: [EMAIL PROTECTED] Subject: Linux equivalents of Unix commands? Our new WebSphere administrator is wondering if there are Linux equivalents of prstat and pstack. Didn't find them in the distribution media that I have. Are there Linux versions of these? -- 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: Permissions on Samba Printshare files
When print files appear in the printshare, they belong to xgroup,
but they have permissions as 600, instead of our intended 660. In
this printshare, that's important because the files don't go straight
to a printer. Instead, a process picks them up and modifies them.
Our work-around is to use the printshare's print command to do a chmod
on the incoming file.
After some experimenting, I suspect that Samba assigns 600 to a
printshare file regardless of contrary parameters, but I have been
unable to find any Samba documentation that verifies this.
Could anyone confirm that Samba forces 600 permissions for printshare
files? OR - have I overlooked something in our set-up?
This is no configuration oversight on your part. You are correct, Samba
does not consult force create mode when opening the spool file. It
uses smb_mkstemp which is:
int smb_mkstemp(char *template)
{
#if HAVE_SECURE_MKSTEMP
return mkstemp(template);
#else
/* have a reasonable go at emulating it. Hope that
the system mktemp() isn't completly hopeless */
char *p = mktemp(template);
if (!p)
return -1;
return open(p, O_CREAT|O_EXCL|O_RDWR, 0600);
#endif
}
~ Daniel
--
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: Permission denied on Samba 3.0.9-17 download.
URL: http://ftp.sernet.de/pub/samba/sles8-s390/ Works now ~ Daniel -- 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: Permission denied on Samba 3.0.9-17 download.
Can whomever it is that maintains this please open up the permissions on the files? Brandon, I've let Volker L know... I seriously doubt he's on this list. In the meantime if you are very anxious, I can send you a samba3-3.0.9-17.src.rpm. I can also send you s390 compiled rpms, but cannot guarantee they are the same as SerNet because I built them before the sernet s390 rpms were available. Let me know offlist... I'd want to check to make sure I didn't leave any of my crap laying around in the spec first. ~ Daniel -- 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: Adding an additional volume using LVM
was the issue of umounting the lvm. Everytime I was issuing the umount /dev/system/samba I received an error msg device busy. Fortunately I knew which other linux servers had the share mounted (via nfs) and closed down that service to be able to umount it. How would I be able to assertain what servers had the share(s) attached ? fuser (path) will list the processes ~ Daniel -- 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: Security alert for SMBFS - Anyone know anything?
Anyone seen this? http://www.securityfocus.com/bid/11695/info Yup, it requires you to mount a smbfs filesystem from a hostile system onto linux. This is a different animal than samba. This is a network filesystem mounted kind of like nfs (fs type will say smbfs). If you don't have users mounting file shares onto your linux servers using smbfs, this should not affect you. The reverse... windows clients mapping samba shares from your server onto their PC is something different. ~ Daniel -- 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
VM dispatching
A few weeks ago we had what over time grew into a big problem dispatching guests. Guests would stop being dispatched sometimes for 10 minutes at a time, for no reason that we could identify. Usually shutting some guests down would get everyone dispatching again, but it was a mess. We applied some VM PTF's (like UM30888) and things got much better, but there are still times early in the morning where our performance guy's accounting records show the guests getting zero cycles in a minute interval or two. For example, last Wednesday a few guests got zero cycles (averaged over minute intervals) at 00:23:00-00:25:59, and this morning it was 4 guests from 00:21:00-00:23:59 (specifically linintra 00:21:00-00:23:59, linsmtp 00:21:00-00:22:59, linwsm 00:21:00-00:22:59, linps1 00:22:00-00:23:59). An IND Q shows that we now have non quick dispatch guests running in queues other than Q3, which is different than from before the PTFs (we are on z/VM 4.3 Guestlan). IND Q TCPIPII Q0 PS 0419/0084 AI00032 Q1 R00 1165/1144 TCPIP Q0 R 1054/0367 LININTRA Q2 PS 00012923/00012885 LINPROXY Q0 PS 00015499/00015461 LINSMTP Q1 PS 00012242/00012183 LINFS1Q3 PS 00045610/00053128 LINPS2Q1 PS 4611/4544 LINPOPQ3 PS 6052/5455 LINFS3Q3 PS 00024126/00038166 LINFS2Q3 PS 00054785/00065536 LINUX1Q3 PS 6535/7603 Occasionally we will see these messages in linux syslog: Nov 17 00:25:14 linpop kernel: addrconf_verify(): too slow; jiffies - now = 63 We run the guest's storage pretty tight on the linux side; our largest three images are 256MB (the samba file servers), with VDISK allocated as needed (our most active one right now has another 256MB split over 4 VDISKs). Our smallest guest is 32MB. Are there any VM commands we can use to get a better idea why VM might stop dispatching some of the guests temporarily, or any other ideas/suggestions anyone can offer? Thanks, ~ Daniel -- 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: Problems with SLES 9 and guest lan
I have a 64-bit SLES 9 test system that I've been playing with. I recently applied some patches that Suse had recommended applying. After I recycled the system, it will no longer talk to the guest lan. It worked prior to the patches and no changes have been been made on the VM side. It could have been a kernel upgrade without running zipl. Does the version returned by uname -r match something in /lib/modules/? ~ Daniel -- 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: problems during sles9 installation
What was the amount you gave it (for those that follow)? The doc said 256MB+ for nfs, 512MB for ftp/VNC. I had 256MB plus some swap (which the installer activated), and at the time of the failure this looked like more than enough. The system was up to 110MB just for buffer/cache with another 58MB unused and about two thirds of my swap free. # free total used free sharedbuffers cached Mem:253536 194608 58928 0 58136 51900 -/+ buffers/cache: 84572 168964 Swap: 107896 39684 68212 After increasing to 512MB the installer made it through zipl on the first attempt and finished writing the final configuration. I didn't try anything between 256 and 512... or try it again. ~ Daniel -- 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: problems during sles9 installation
From a different client I can consistently get through most of the
install up to zipl segfaulting. When YaST2 attempts to reinstall the
bootloader, and it hangs. 100% repeatable for me.
- What type of disks?
- Amoung of memory?
ECKD DASD (CDL formatted)
256 MB memory, plus the installer uses the specified device for swap.
I'm using NFS because it's the lightest. Zipl segfaults with both X
over ssh, and a straight ssh (ncurses) install.
# free
total used free sharedbuffers
cached
Mem:253536 194608 58928 0 58136
51900
-/+ buffers/cache: 84572 168964
Swap: 107896 39684 68212
Here are the console messages from the zipl segfault:
illegal operation: 0001 [#1]
CPU:0Not tainted
Process pdflush (pid: 12, task: 0f694e48, ksp: 0f675da0)
Krnl PSW : 07081000 8002 (0x2)
Krnl GPRS: 0003 0e54f100
005d 0f675af0 0001 0e54f1a4
0094 0f675e18 007380a0
0e54f100 80192188 801928a8 0f675a08
Krnl Code: 00 00 80 10 ed ac 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Call Trace:
[00147118] do_writepages+0x44/0x48
[00191658] __writeback_single_inode+0x15c/0x2c0
[00191c04] sync_sb_inodes+0x174/0x2f8
[00191fee] writeback_inodes+0x106/0x1b4
[00147530] wb_kupdate+0xe0/0x16c
[001479a8] pdflush+0x194/0x26c
[00131304] kthread+0x118/0x140
[00108296] kernel_thread_starter+0xe/0x14
illegal operation: 0001 [#2]
CPU:0Not tainted
Process zipl (pid: 8812, task: 0e7cd718, ksp: 0fb01af8)
Krnl PSW : 07081000 8002 (0x2)
Krnl GPRS: 0001 08cfc900
0001 0fb01b28 0001 08cfc9a4
0014 0fb01df0 00666fa0
08cfc900 80192188 801928a8 0fb01a40
Krnl Code: 00 00 80 10 ed ac 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Call Trace:
[00147118] do_writepages+0x44/0x48
[00191658] __writeback_single_inode+0x15c/0x2c0
[00191c04] sync_sb_inodes+0x174/0x2f8
[00191e22] sync_inodes_sb+0x9a/0xb0
[00191e80] sync_inodes+0x48/0xb0
[0016bfc8] do_sync+0x44/0x90
[0016c07a] sys_sync+0x66/0x9c
[0010e876] sysc_do_restart+0xe/0x12
I re-IPLed the installation image and just after activating the dasd
devices, I mounted/chrooted and re-ran zipl from a second session. It
completed this time... but I don't know what yast does after zipl.
After ipling from DASD this time, the guest came up without its GUESTLAN
interface (only loopback). We're still on VM 4.3 so use GUESTLAN, there
was no chandev.conf (2.6?) and modules.conf was empty. I couldn't ssh
in so sent ^C at the console to try to get a shell there and all the
SuSEConfig stuff kicked off (I hadn't yet been able to run
YaST2.sshinstall) so I logged off. Any suggestions?
The md5sums on the .isos match what is listed on portal. Don't know if
it helps, but here's some info about the zipl that segfaults during
installation the first time and hangs the second time:
inst-sys:/sbin # md5sum zipl
38e33533797accdbe1aba7eb26072d99 zipl
inst-sys:/sbin # ls -l zipl
lrwxrwxrwx 1 root root 25 Nov 16 10:44 zipl -
/mounts/instsys/sbin/zipl
The second time zipl is run, ps shows it usually in D+, but occasionally
R+. I let it run for a couple of hours, I never caught it with a
different PSW than:
inst-sys:/proc/9438 # cat status
Name: zipl
State: D (disk sleep)
SleepAVG: 116%
Tgid: 9438
Pid:9438
PPid: 9437
TracerPid: 0
Uid:0 0 0 0
Gid:0 0 0 0
FDSize: 32
Groups: 0
VmSize: 1520 kB
VmLck: 0 kB
VmRSS: 588 kB
VmData: 152 kB
VmStk: 8 kB
VmExe:76 kB
VmLib: 1156 kB
Threads:1
SigPnd:
ShdPnd:
SigBlk: 0800
SigIgn: 1002
SigCgt:
CapInh:
CapPrm: feff
CapEff: feff
task: 0fc36e38, ksp: 0cf3faf0
User PSW : 070de000 c00cd6a2
User GPRS: 400cd6a0
80409d9a 004160e8 7b38
00401110 00493130 79e0
00416008 80409b6c 80409dce 7968 User ACRS: 40144460
~ Daniel
--
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: problems during sles9 installation
can you give more memory to the guest (just during the installation phase)? The SLES9 install completed cleanly after giving it more memory. Thanks, ~ Daniel -- 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: problems during sles9 installation
Where did you get the documentation on doing an upgrade from sles 8 to sles 9? TIA! There's a docu directory in CD1 (SLES-9-s390-RC5a-CD1.iso). I didn't look to see if the doc addresses upgrading, but it was an option during the install process. I'd poke around on CD1 first... there were several pdf and text/html files there. ~ Daniel -- 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: problems during sles9 installation
Looks like the kernel has some definite problems. If this is as repeatable as it sounds, I would report it to SUSE, and perhaps the LKML. I switched from a coworkers machine to my linux box here and things are a bit better. Now twice I've made it all the way through the install up to zipl segfaulting. I'll give our support line a call... ~ Daniel -- 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
problems during sles9 installation
I didn't see anything in the installation doc so I thought I'd ask if anyone has seen this before: I'm trying a new install of SLES9 (s390 31bit) under VM. I had previously formatted all the DASD from another SLES8 system. The install was working on the second CD (core9/CD1) over NFS (loop mounted isos) with an ssh client. Several progress bars into it, the ssh client disappeared and this was written to /var/log/messages... Nov 15 19:58:22 suse kernel: JBD: barrier-based sync failed on dasde1 - disabling barriers Nov 15 19:58:22 suse kernel: JBD: barrier-based sync failed on dasdf1 - disabling barriers Nov 15 20:13:18 suse sshd[245]: Received signal 15; terminating. Nov 15 20:13:18 suse kernel: illegal operation: 0001 [#1] Nov 15 20:13:18 suse kernel: CPU: 0 Not tainted Nov 15 20:13:18 suse kernel: Process linuxrc (pid: 292, task: 0f849b70, ksp: 0e433ea0) Nov 15 20:13:18 suse kernel: Krnl PSW : 07081000 8002 (0x2) Nov 15 20:13:18 suse kernel: Krnl GPRS: 0001 073b6500 Nov 15 20:13:18 suse kernel: 0036 0e433b28 0001 073b65a4 Nov 15 20:13:18 suse kernel: 0295 0e433df0 006ab360 Nov 15 20:13:18 suse kernel: 073b6500 80192188 801928a8 0e433a40 Nov 15 20:13:18 suse kernel: Krnl Code: 00 00 80 10 ed ac 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Nov 15 20:13:18 suse kernel: Call Trace: Nov 15 20:13:18 suse kernel: [do_writepages+68/72] do_writepages+0x44/0x48 Nov 15 20:13:18 suse kernel: [__writeback_single_inode+348/704] __writeback_single_inode+0x15c/0x2c0 Nov 15 20:13:18 suse kernel: [sync_sb_inodes+372/760] sync_sb_inodes+0x174/0x2f8 Nov 15 20:13:18 suse kernel: [sync_inodes_sb+154/176] sync_inodes_sb+0x9a/0xb0 Nov 15 20:13:18 suse kernel: [sync_inodes+72/176] sync_inodes+0x48/0xb0 Nov 15 20:13:18 suse kernel: [do_sync+68/144] do_sync+0x44/0x90 Nov 15 20:13:18 suse kernel: [sys_sync+102/156] sys_sync+0x66/0x9c Nov 15 20:13:18 suse kernel: [sysc_do_restart+14/18] sysc_do_restart+0xe/0x12 Nov 15 20:13:18 suse kernel: SuSE Instsys linfs3:/ # We've tried fresh a few times... I've verified that the md5sums of the isos match what SuSE reports as correct. Everything seems in order, except for the installer crashes. Has anyone seen anything like this? Thanks, ~ Daniel -- 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: Documentation for User Process Faults
knowing how to interpret the User process fault: interruption code messages that get generated. Is there a pointer to a document that contains explanations for these that anyone knows about? You've probably already seen this, but just in case... there's a tiny bit in linux/arch/s390x/mm/fault.c 0x04 Protection 0x10 Segment translation 0x11 Page translation 0x3b Region third trans. ~ Daniel -- 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: Guest freeze
If you watch the console long enough, do you see anything like: __alloc_pages: 0-order allocation failed or VM: killing process? How large did you define the guest? How much is a small amount of swap? What kind of workload? What error message do you get when you try to log onto the linux console? Also, by default SLES8 kicks off sa every 10 minutes. If you're lucky you might get one of these hangs shortly after one of these 10 minute intervals. It might be interesting to check out the system activity data. Something like: /usr/bin/sar -u -r -f /var/log/sa/sa.2004_09_15 You can further narrow it if you want by specifying a start and end time, like: /usr/bin/sar -s 08:00:00 -e 09:00:00 -u -r -f /var/log/sa/sa.2004_09_15 ~ Daniel -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Troyski Sent: Wednesday, September 15, 2004 6:58 AM To: [EMAIL PROTECTED] Subject: Re: Guest freeze Just to let you know; I removed the samba client RPM from two of my guests that exhibited the hang problem, but one at least one still shows the problem. I still think the problem is memory-related, possibly a memory leak as the guest that hung had reached 99% of memory and 100% of swap (abeit a very small amount of swap) just before it hung. Troy. On Tue, 14 Sep 2004 13:32:10 -0400, Joe Poole [EMAIL PROTECTED] wrote: We've seen it when a Samba smbd session goes into a loop when someone, probably trying to back up his C drive, or store the family jpegs, runs the server out of space. The solution is to find the process ID with TOP and kill that session. On Tuesday 14 September 2004 13:20, you wrote: Do you know what specifically triggers the problem? I was just asked if we could do samba. Seader, Cameron [EMAIL PROTECTED] er.com To Sent by: Linux on [EMAIL PROTECTED] 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: Guest freeze 09/14/2004 08:33 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Here is some more information about what we had discovered after talking with SuSE. This problem was never resolved. Just an update on the bug found yesterday. I just got off the phone talking with Novell's SUSE support department and we were able to narrow down which package was causeing the conflict with the openldap2-client library. Samba-2.2.8a has a service called nmb which is the netbios service, which has hooks in the openldap2 library files. We were able to narrow down to the service nmb when it is started it causes a loop process to start in the kernel process ksoftirqd_CPU0. This investigation has been sent off to the Development labs at SUSE in Germany. They will either find a fix for the current package and send that out globally, send us a beta version of SLES 9 (which is on beta 2 right now), or they will have us wait until SLES 9 is released. Another option is to download the Samba 3.0 binaries and compile it for our platform ourselves, which would go out of the support bounds for SUSE. -Cameron Seader -Original Message- From: Troyski [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 14, 2004 07:13 To: [EMAIL PROTECTED] Subject: Guest freeze Hi all, Anybody seen the following conditions :- o VM linux guest hangs. No response to ssh or at 3270 console. Pings from other servers (external and internal) ok though (?) o VM CPU @ 100%. o No VM paging. o VM guys say linux is looping. zSeries 800/SLES8 SP2 Would a linux guest memory issue cause this? -- 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: Guest freeze
Hi Daniel, I have seen the __alloc_pages message in /var/log/messages as well as the VM: Killing process message. So you are definitely short on storage. Which is why you can get ping responses, but no new shells/processes forked to log on. One of the guests is 1280Mb, the other 1792. They were initially sized at 1024 and 1536 to accomodate the number of websphere JVM's that are deployed. And these don't seem too skimpy either. snip Both guests have a 19188k swap disk (VDISK) defined. That does seem low considering your real storage sizes. I am using grinder to put the guests under load, but this is no where near the sort of load I want to achieve. The grinder test runs for approx. 2-3 hours before a guest will hang. Is grinder running on these guests or somewhere else? If it's running on the same image as the one you are load-testing, is it possible that grinder is chewing up significant resources... stealing from what would be Websphere's resources? Top may tell... ~ Daniel -- 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: Guest freeze
Grinder is running on an external PC. So it's not that. Good call though. Don't know if you've used this or not, but here's a quick installation thing that may help to determine if your storage sizes are realistic or not... http://www-1.ibm.com/servers/eserver/zseries/os/linux/pdf/avmlinux.pdf Also, I think there may have been some WebSphere garbage collection or storage tuning threads on the list previously. Here's a starting point at least: http://www.mail-archive.com/cgi-bin/htsearch?config=linux-390_vm_marist_ edurestrict=exclude=words=websphere+garbage Beyond that I'm not sure what to tell you beyond verify that WebSphere is the culprit, but it seems very likely. GL, ~ Daniel -- 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: shmmax
I increased my machine from 32M to 128M. I used the echo 134359738368 /proc/sys/kernel/shmmax Everytime I reboot, the value returns back to 32M. How do I make this permanent on a SLES8 machine ? sysctl called by the startup scripts is the recommended way... check out /etc/sysctl.conf The line will look like kernel.shmmax = value ~ Daniel -- 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: Recycling servers ?
I was told that linux servers have to be rebooted periodically to clear out buffers, cache, storage, etc. Not really. Linux is designed to reclaim/reuse/adjust as needed. Many people are quite proud of their uptimes... If you seem to be losing storage, I'd check on the virtual storage sizes of your long-running user-space programs first. ~ Daniel -- 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: RH 7.2, Apache and MS Front Page Extensions
I'm installing, or trying to, MS Front Page Extensions in my RH 7.2/Apache LPAR. If you've been able to successfully accomplish this I'd like the opportunity to ask some questions. Thanks I don't know if he still does, but when I was using MS FPSE's on RH 7.2 s/390, joshie.com had forums and RH srpms. The srpm included the FPSE tarball for intel binaries, but it was simply a matter of replacing the tgz in the SPEC and SOURCES with the s390 tgz from rtr.com. All the rest of the apache/FPSE build/configuration stuff was identical. It'll be a big timesaver. I think the latest version of FPSE's are a lot cleaner. They came out with a version that slips in and out as a DSO (dynamic shared object), so you don't have to rebuild everything that used apache headers (like mod_php, mod_ssl, mod_python, etc) due to FPSEs messing with them. Check out joshie.com, the FPSE stuff was under projects, ~ Daniel -- 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: Using RPM to install a source RPM
I try a 'rpm --install nano-1.2.3-1.src.rpm' and absolutely nothing happens. rpm -qlp nano-1.2.3-1.src.rpm shows the files that will be unpacked by the rpm. You either want to rpm -bb the_spec_file or simply rpm --rebuild nano-1.2.3-1.src.rpm. Good luck, ~ Daniel -- 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
tivoli storage manager client?
For those that are using the Tivoli client for file-level backups on linux s/390, can anyone comment on their own experiences with Tivoli client resource requirements? We've recently started backing up a new file-server. As it was hitting its 430,000th file processed, top was reporting memory usage of half a gig just for the dsmc process. This was after a suggestion to enable memoryefficientbackup yes (it was just as bad/worse before). The process starts small and just seems to grow continually until finished/killed. In this case the guest was 256M with 360MB vdisk swap (various priorities) and additional dasd swap for relief in case the vdisk fills. There's nothing else really running their yet. Has anyone noticed anything similar? Thanks, ~ Daniel -- 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: tivoli storage manager client?
I've seen that behavior on a system with a lot of open files (it keeps a context entry to go back and check later in the run to see if the file is closed and available), but that doesn't seem to be the case here. Is this the first backup of that filesystem on this server? Sometimes the first backup does consume a lot more resources than the future incrementals. In this case, no, the files weren't opened. We have yet to complete a backup on this server, but it's no longer sending files across... It'll just be doing the: 08/18/04 22:24:34 ANS1898I * Processed 4,000 files * 08/18/04 22:24:35 ANS1898I * Processed 5,000 files * 08/18/04 22:24:36 ANS1898I * Processed 7,000 files * 08/18/04 22:24:41 ANS1898I * Processed14,000 files * 08/18/04 22:24:42 ANS1898I * Processed16,000 files * 08/18/04 22:24:43 ANS1898I * Processed17,000 files * 08/18/04 22:24:47 ANS1898I * Processed22,000 files * 08/18/04 22:24:50 ANS1898I * Processed26,000 files * 08/18/04 22:24:54 ANS1898I * Processed30,000 files * messages, etc, because these files have not been opened/modified since the last dsmc. Yet the dsmc footprint quickly skyrockets. But, that said, no, that's not unusual. The TSM client is a pig for resources. Thanks David, ~ Daniel -- 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: tivoli storage manager client?
Guessing (WAG mode): Could this memory growth be caused by maintaining symlink context? It strikes me that if there are a lot of symlinks that there'd need to be kept a list of where they're pointing so that it could ensure resolution. Since I've *NO* knowledge of the internals of TSM (I have enough problems getting time to understand the externals) the above is a WAG. It's a good thought, but typically these sorts of programs just keep a history of directory device/inode number pairs to identify some kind of symlink recursion. Those two numbers are enough to uniquely identify any file/directory on a system. That, and there aren't any symlinks on that mountpoint, but nothing is there to stop dsmc from keeping track of it anyway... Thanks for thinking about it. ~ Daniel -- 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: Slack/390 issue: no login prompt on vm console [Virus checked]
I don't get a login prompt. But I do get the # sign and can enter commands. I'm using Hercules, the 390 emulator. This is in /etc/inittab 1:012356:respawn:/program/to/run Is it just /bin/bash now? You might be looking for something like /sbin/sulogin, or /sbin/sulogin -t 30 You can modify /etc/inittab, kill -HUP init, then kfrom the console, close the currently spawned shell with exit. The next one to be created should be whatever is in your respawn line. Beats rebooting just to pick up the configuration change, anyway. ~ Daniel -- 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: Model 27 dasd
Has anyone created an LVM from multiple mod 27's (32,720 cylinders) ? Wasn't any different than 3's or 9's for us. Only thing I can think of is you might want larger logical volumes now that you have larger PVs, so your -s parameter on vgcreate might be larger. http://linuxvm.org/Info/HOWTOs/lvm.html Also, if your LVM is not going to be resized, people tend to prefer striping across many smaller ones for throughput. But no problems; everything's the same only bigger :). ~ Daniel -- 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
VM TCPIP guest router not on GLAN?
This past weekend we had our DR test, and while my linux guests came up and could talk to each other on the GLAN, none could contact the vm TCPIP router/gateway (or send traffic outside the virtual network). A #CP Q NIC DETAILS from the linux guests showed TX Packets getting discarded, presumably because the router address was not coupled with the guest lan? TCPIP was up and we could ping the router address from outside, but none of the linux images from the outside. Any idea what step was missing... how to get the vm TCPIP guest on the glan again? Apart from how to get it working again, we're curious why it didn't come up automagically in the first place. There are a few potential culprits, as VM could not be started WARM (replied FORCE). Also, it was VM under VM, and the first time we tried to bring it up the OSA on 1st level VM was defined odd-even-odd. But we shutdown, got it redefined even-odd-even, and started again (this time WARM). Like I said, we could ping the router from the outside, and none of the glan guests from the outside, and on the inside we could ping all the glan guests but not the vm tcpip router. Thanks for any ideas, ~ Daniel -- 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: VM TCPIP guest router not on GLAN?
G'day Vic! and either VM TCPIP had the wrong IP address (at the Guest LAN interface) In this case would the ping to the gateway ip address from the outside have succeeded? or the TCPIP machine was not attached to the Guest LAN. For future reference... how would we reattach it :)? They tried a: DEFINE NIC 700 QDIO DEV 3 COUPLE 700 SYSTEM VMGLAN from TCPMAINT, but I think it should have been done for TCPIP instead. How would they have done that? Depending on how your routing is set up, it might also have been a problem with the route table on VM TCPIP. Is this also found in PROFILE TCPIP? Thanks, ~ Daniel -- 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: Network freezes
connections are going down, e.g. all ssh sessions get lost with timeout etc. A ping doesn't reach the linux. Pings from direct network-neighbours to the linux fail, too. snip (around 20-45 minutes), suddenly the linux answers again. There are no error-messages in /var/log/messages. Sounds like your guest is not getting dispatched. Does a #CP IND QUEUE when this occurs show that guest in a queue or an eligible list? If the guest is stuck in the eligible list, you probably want to tweak srm settings and/or reduce some of your guests storage sizes. ~ Daniel -- 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 under VM and Cloning
We are going with a lot of Linux Guests under VM. Close to 20 per IFL and are wondering about the experiences with the basevol/guestvol scenario. How many People accually use this scenario? How much DASD does this really save you? Is it worth the time and effort it takes to set this up? Could you just setup Links to specific disks in VM for a Guest like if you just wanted to share the binaries for say Oracle, or the /usr directory or /home directory? Wouldn't this accomplish the same thing? What would be the best way to go about this? It seems that you would definately save on DASD, but how much is the Question. Does SUSE support the basevol/guestvol out of the box, or are their some packages that need installing to make this work? How stable is it running under this basevol/guestvol scenario? hopefully this is not too much to ask question wise. Thanks in advance We ran with a variation on basevol/guestvol when we were initially trying out RH 7.2. The only difference was that we had multiple guestvols per image split by mountpoint, so someone filling up /home would not impact /var (like it would have with the single-filesystem guestvol). At any rate, the DASD savings for each of your guests are as large as the basevol. There are also nice security perks, as your binaries are all RO even to root, etc, which is another layer of protection against bad things happening, accidental or otherwise. However, it was difficult to get the maintenance onto the RO devices without significant disruptions to the guests when running with the basevol/guestvol model, so when we switched to our SLES8 eval we abandoned basevol/guestvol with the intent of reconsidering it in the future. This was our first SuSE install, we weren't sure how much we'd tweak our base image, and the hoops we needed to go through to update any package on the RO basevol was a little painful. Right now we only have around 10 guests, so it's still manageable, but if the numbers start increasing then we may go back to a basevol/guestvol-type system. The initial time and effort was rather small, the real issue was the effort that went into applying any updates and keeping the rpm database current on each guest. Stability was no problem. Rather than go the basevol/guestvol extreme, I think most people doing DASD sharing just do specific mountpoints like /usr readonly. You mention /home, and you typically wouldn't have /home RO, but anything that can be RO across images (particularly filesystems that rarely need updating) can be shared. Just ensure that any minidisks linked RO are added to the linux dasd device driver ro (like with zipl.conf parameters=1000(ro),...) in addition to your fstab. This approach is more directly supported out of the box, as the basevol/guestvol approach will require some minor customization of the SuSE startup scripts and is a bit exotic, but having a mountpoint or two like /usr RO is fairly common practice. ~ Daniel -- 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 under VM and Cloning
On Thursday, July 08, 2004 10:48 AM Adam Thornton wrote: On Thu, 2004-07-08 at 09:41, Daniel Jarboe wrote: the real issue was the effort that went into applying any updates and keeping the rpm database current on each guest. Stability was no problem. I haven't found a better way to do this than a sacrificial clone of the pre-service basevol attached r/w to each guest before you apply the per-disk service. After you've done that, reIPL the guest with the shared (updated) r/o disk, and reimage the sacrificial disk with the pre-service state, and move on to the next guest. Is there a better way? We arrived at our process after quite a bit of discussion on the list... someone was doing something similar to what we ended up with. We did the rpm -Uhv's on a copy of the current production basevol (not each guest), and then ipled each guest off the basevol during that guest's window. BUT, before we applied the maintenance on the basevol, we manually checked to ensure that that upgrade did not change guestvol files. Also, we manually checked rpm -qp file.rpm --scripts to ensure nothing there would touch guestvol files. In all our RH rpm updates, I don't remember any needing special action on the guests except maybe a one-liner a single package needed to rebuild a file. This required us to run that script on each of the guests, but this too we put in the startup scripts on the basevol so the guest could do it automatically the first time it came up, based on whether a file existed on the guestvol. Nothing fancy, but it was sufficient. It still required an IPL of the guest just to update one measly binary, though, because everything was shared RO. We also shared the rpm database r/o, but that isn't necessarily a requirement. You can rpm -Uhv --justdb the maintenance on each of the guests if you want each to have its own R/W rpm db without adding a second db. Again this worked because except for rare exceptions, the maintenance never changed guestvol files. For new package installs, you'd need to get the guestvol files there, but again this could be automated in the basevol startup scripts by checking if a file existed and if not untar a tarball. ~ Daniel -- 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: Change IP addr!
Hello I am changing the ip addr of the suse server on s390, in redhat I can change in /etc/sysconfig/network-script.. but... where can i change in suse 8.. ? You change it in /etc/sysconfig/network/ifcfg-eth0 (where eth0 is your interface name). Or for overkill use YaST ~ 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: J2EE performance?
- Rapid software development - Lesser quality code, with less efficient use of resources - Higher resource demands - Higher minimum requirements for the application The reason I usually hear: It used to be that your people's resources were inexpensive compared to hardware. When it turned the other way around (especially for PCs), development shifted dramatically to reflect the change. Spending the additional resources to write higher-quality code just didn't pay anymore. Good enough was, well, good enough (and cost a lot less). ~ 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 -- Drivers not downloading to Windows Client
I was successful in getting my Window's printer driver (for an HP 4600) to upload to the Samba directory /usr/lib/samba/drivers/3 I used the Windows client to do this, by following the instructions in Mike's redpaper...Cups Samba Typically it's /usr/lib/samba/drivers/W32X86/3 What's your smb.conf? How did you upload the drivers? ~ 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: Upgrading Samba to 3.0.4 on SLES8
The main reason that I suggest this is because there seems to be a nasty bug in Samba (s390) whereby TDB files become corrupt under a significant workload. Samba must be recycled to work around the TDB corruption. This is being addressed in PMR 68139. There is a workaround to use the smb.conf global mmap = no which seems to avoid the problem in Samba 2, but not in the latest Samba 3. FYI, the workaround should be effective again since svn commit 1011, but there's no GA (or even pre or rc) release of Samba that incorporates the changes yet. Even still, Is there a specific function you need in Samba 3 that is not available in Samba 2? If not I would recommend sticking with the distro-supplied RPM. This advice still holds! ~ 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: ftp.suse.com samba3 vanished?
Went to see if there were any samba3 package updates for s390 today and found the following link no longer valid: ftp://ftp.suse.com/pub/people/gd/samba3 Anyone happen to know if that's officially gone or just maybe moved to another location on their site? I don't know what became of Guenther Deschner's directory there, or where his Samba 3 packages can now be found, but you can still find Volker Lendecke's at sernet.de (originally based on gd's). http://ftp.sernet.de/pub/samba/, ftp works too. HTH, ~ 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: Initial LPAR install zSeries
Has anyone done a LPAR install on zSeries and then migrated to a zVM infrastructure ?, any ideas on this ?. Yes, we started this way. Migration was painless. I would look at the LPAR install just so that we get a head start on the project , the zVM is part of the IBM bundle that will come a little later in the project. It's easy enough to do. We ended up installing VM in the same LPAR, which meant we had to shut down our linux image for awhile while the VM install/config was going on. Then in the system directory of VM we dedicated the LPAR resources the image used to the new guest, ipled the guest, and everything came up fine. Eventually we copied the data onto vm minidisks proper. We were using CTC to another LPAR at the time, which worked without any changes under VM. A week after getting the image up under VM, though, we moved to GuestLAN. HTH, ~ 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: Hipersockets defined to VM guest - not showing up in examination of /proc/chandev
Even if I have not defined them to the linux guest itself, if they've been dedicated to the VM guest ID, a cat of /proc/chandev should show me the devices right? /proc/subchannels? ~ 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: Hipersockets defined to VM guest - not showing up in examination of /proc/chandev
Even if I have not defined them to the linux guest itself, if they've been dedicated to the VM guest ID, a cat of /proc/chandev should show me the devices right? Yes, they should. In use and chandev reg will be no. Are they not there? Do they show up in /proc/subchannels? ~ 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: ld-linux.so.2
linuxdev:/home/hrive # rpm -iv gcc_old.rpm error: failed dependencies: ld-linux.so.2 is needed by gcc_old-2.95.3-92 Can you help us resolve this? Where can we find ld-linux.so.2. It is not on the Operating System CD's. Where did you get this rpm? The gcc_old provided with SP3 for 31-bit does not have this dependency: $ rpm -qp --requires gcc_old-2.95.3-4.s390.rpm binutils compat /bin/sh ld.so.1 libc.so.6 libm.so.6 libstdc++-libc6.2-2.so.3 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libm.so.6(GLIBC_2.0) rpmlib(PayloadIsBzip2) = 3.0.5-1 I see you are running 64-bit, so there may be some differences, but are you sure your gcc_old rpm is compiled for the distro you are running? There are some symlink to ld-2.2.5.so tricks you could try, but you should avoid headaches and get the correct gcc_old rpm... ~ 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: Adding a new DASD
-add the line : MDISK 0204 3390 0001 3338 VMLX05 MR ALL SOME FEW into my Linux CMS user's USER DIRECT definition. - Format the device using cpfmtxa z/VM utility. - CMS format 204 c - IPL my Linux system. - check the devices: cat /proc/dasd/devices Does it show up in /proc/subchannels? If so, add it to the dasd device driver with: echo add range=204 /proc/dasd/devices If not, the guest can't see it for some reason (did it get detached?) 0201(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 581040 blocks , 2269 MB 0202(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 600840 blocks , 2347 MB 0203(none) at ( 94: 8) is dasdc : unknown After the add range to /proc/dasd/devices you should see a dasdd entry here. Pick up where you left off with the dasdfmt, then fdasd, then make the filesystem on /dev/dasdd1 (or whichever partition) and you should be golden. Don't forget to add the address to your dasd= parameters in your zipl.conf, cd /boot and run zipl so the dasd device is automatically enabled the next time you ipl. ~ 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: password for root on Gentoo for S/390
OK, what's the password for root when installing Gentoo for S/390 from the Stage3 file? I think it was for the x86 stage3 live cd... try that. ~ 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: password for root on Gentoo for S/390
OK, what's the password for root when installing Gentoo for S/390 from the Stage3 file? I think it was for the x86 stage3 live cd... try that. Or random/not-set? Can you not set your own with passwd at the console...? ~ 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: password for root on Gentoo for S/390
I'm working with the Stage 3 install which is a pre-generated system. I tried to do a passwd root newpasswd after performing a chroot /mnt/gentoo. I suspect this changes the password on the driving system. I made sure I changed root's password to the same one I'm using on the driving system just in case this is true. If this is true then I don't know how to update the password for root on the target system. The passwd command after your chroot /mnt/gentoo changes the password for the chrooted (target) system. The idea of chroot is that you are not able to modify files outside of the the chroot environment without jumping through hoops/bugs. When you were chrooted it was files in /mnt/gentoo/etc/ that were updated, not in /etc/. ~ 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 V2 - Can I join a Windows ADS Domain which is in mixed mode??
Question:
Can Samba V2.2.8a join an Active Directory domain (which is running
in mixed mode)
as a domain member... and does WINBINDD work in that environment?
Yes, Samba 2.2 is basically a NT-type client. If NT clients can
participate in the AD, so can Samba 2.2.
But winbind doesn't want to start:
smb.conf does not contain windbind defs
id map...unknown parameter or invalid range
You should have a few things set
security = DOMAIN
workgroup = {whatever the name of your domain is}
winbind uid = 1-2 (or something appropriate for you)
winbind gid = 1-2 (or something appropriate for you)
Also, you can optionally fiddle with winbind enum users, winbind enum
groups, winbind use default domain, etc.
With winbind running, you'll want to make sure nscd isn't, and that
winbind is in the passwd and group lines of your nsswitch.conf. And
make sure the libnss_winbind.so - libnss_winbind.so.2 symlink is there.
GL,
~ 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
OT, but a familiar face
Hope people don't mind the OT post, but in rationalizing, it's pretty easy to connect the dots from Jay Maynard to Hercules to Linux s/390... http://www.ibiblio.org/jmaynard/TRONcostume/ ~ 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: DASD Errors due to R/O
Thanks. The document I am using to build this environment says that if I do that then I will not be able to access the R/W DASD even from the ID i used to build them since all systems will not see the DASD as R/O. If there a way around that? Your R/W guest should not update the dasd that others have linked to and are using. You run into filesystem buffer/consistency problems because the guests do not know that others are using the dasd too. Is your basevol volume listed in the boot parameters of the R/W guest? If it is, it probably shouldn't be (just add it to /proc/dasd/devices when you are doing maintenance and the other guests are not using it). dasd=1F0-200,201(ro),202-21F However note that this cannot be done from the guestvol system, since the boot device is R/O. And if this is done from the basevol system you will no longer be able to write to the boot device to maintain it in the future. Here they are saying it is impossible for guests to write a new ipl record (with 201(ro) or anything for that matter) from the guest system because VM won't let the guest write there. So (unless you are using Leland's patch to get the parms from somewhere else), you run zipl with the 201(ro) line targeted at the basevol from the guest that can write to the basevol, then when the RO guests ipl off the basevol the dasd driver sees in the kernel parms that the device should be ro. ~ 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: IBM Plans to Build Servers That Act Like Mainframes
See: http://www.nytimes.com/2004/04/28/technology/28blue.html (Free subscription required) For privacy-paranoid, a lot of news sites (like NYTimes) do not require subscription info if your HTTP_REFERER is from google.com. If your client doesn't support changing this you can always search for the link in question, and google will provide a link for you (If the URL is valid, try visiting...). OT, but some have strong feelings about it, ~ 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
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
VM linux console and @ symbol
Any idea how to get the @ symbol to work when using the VM console for linux. It doesn't matter if I use x3270 on linux or a windows-based 3270 client, @ always seems to be treated as a backspace. Command: echo [EMAIL PROTECTED] becomes echo 134 Command: echo [EMAIL PROTECTED] becomes echo 1234 Command: echo 12@@34 becomes echo 34 Is there some way to escape the @ sign so it doesn't get treated as backspace? Thanks, ~ 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: vsftpd troubles
I am trying to diagnose a problem with vsftpd on sles8 (31 bit). Certain windows clients seems to hang for a long time before getting started. Also they cannot rename/delete files. Other clients work OK. Has anyone experienced this Windows client like %windir%\system32\ftp.exe or windows client like explorer? This sounds like it's probably different, but I experienced a problem with the windows explorer client (different ftp server) under a special circumstance (we were using nss winbindd on the server). I tracked it down to the user's default group Domain Users. The windows client really didn't like a space in the group Domain U. It got confused when it came to the size/date/name portion of the output after there was a space in the group. Modified the source to replace ' ' with '_' in the user/group code, and all was well again. Not sure if vsftp is similar, but you might be a config option for it to only show numeric id's which should work just as well without patching the source. Probably not your problem though :\. Also the output from tcpdump (tcpdump-3.7.1-158) is unlike that which I am used to from sles7's tcpdump (not to mention my i386 SuSE 9). It does not seem to be interpreting the output and only give a hex dump like this 12:05:03.631567 40:0:ff:6:52:b5 45:0:0:28:0:0 0af9 40: 898a 0af9 899e 803d 0015 cc51 523f 5004 e7e2 when I am expecting something more akin to 12:11:51.915179 11.111.111.111.domain lnx.NNN.NN.NNN.33299: 16857 NXDomain 0/1/0 (109) (DF) Anyone know how to persuade it to give a more readable output? There's a tcpdump-qeth.pl wrapper. Not sure what package it comes with, but can be found here http://www.homerow.net/zlinux/tcpdump-qeth.htm ~ 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
for i in `rpm -qa`; do rpm -V $i; done |grep missing rpm: only one major mode may be specified Those are backticks around rpm -qa (on my keyboard, upper left, shared by ~). ~ 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: Sharing root mdisk with SLES 8.0
And finally, the pain involved isnt so great, we just installed a linux vm, compiled and installed the packages that we need (postgres 7.4, apache 1.3.29, perl 5.8, etc), then copied the non-standard directories (etc, Do the extra software packages not included in the base get compiled/installed from source, or are you able to still use a dependency manager like rpm/apt? Also, is it possible to apply service to the base image (things like openssl, openssh, whatever) without rebooting the guests? We've based our work in the presentation from William Scully (http://linuxvm.org/Presentations/misc/basevol.html), but we dont use regina and some other things, we have simplified the procedure a lot. How so? ~ 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
It's funny, this is the one I use to clone, and I just went to another instance, found it and copied it back. Once tar was there, it worked great. I really appreciate your help Glad you are back in business now, though the missing binary IS disconcerting. You should probably take inventory and figure out what else is missing, and why... There's probably a shorter way to do this, but: for i in `rpm -qa`; do rpm -V $i; done |grep missing should work for any rpm packages in your database, though it will take a long time to finish. If some of the files listed as missing seem important, you should consider finding them again :). Good luck, ~ 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
SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e:01 ( was Re: Myth of the 1K blocksize on eckd - revisited)
I just put on SuSE SP3. When I IPL'd, it gives me these messages: Loading module dasd_mod dasd=$dasd ... insmod: dasd_mod: no module by that name found Loading module dasd_eckd_mod ... insmod: dasd_eckd_mod: no module by that name found kmod: failed to exec /sbin/modprobe -s -k block-major-94, errno = 2 VFS: Cannot open root device dasda1 or 5e:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 5e:01 HCPGIR450W CP entered; disabled wait PSW 000A 8022CD08 All the modules appear to be in the right place, and the modules.dep has all the right directories in it. Did anyone else experience this when they put on Service Pack 3? Did you check that your /etc/zipl.conf is correct and re-run zipl? When linux first starts, does it report the kernel version that you'd expect? ~ 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize on e
Yes, I checked the zipl.conf and then ran zipl. Does your zipl.conf have a line like ramdisk=/boot/initrd ? If not, you should probably add it (run mkinitrd if you haven't), and then run zipl again. Loading module dasd_mod dasd=$dasd ... insmod: dasd_mod: no module by that name found Loading module dasd_eckd_mod ... insmod: dasd_eckd_mod: no module by that name found When built as modules, the DASD drivers need to be in the initrd or else the kernel has no way of reading them (since the object files reside on DASD). ~ 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: Quagga Installation Questions
I am ready to do the rpm ?bb quagga-0.96.4.spec. There was a method to redirect the output to the terminal and to a file so I can review it. It was a redirection command and for the life of me, I cannot get my syntax correct. Can someone provide me the syntax? Something like rpm -bb quagga-0.96.4.spec /usr/src/packages/BUILD/quagga-build.log 21 should work. This will redirect your stdout and stderr, and run the build in the background. Once the rpm binary is built, is there anything I can do to test/verify that everything is ok before actually installing it? If rpm -bb gets far enough to write rpm files, you are well on your way. Only thing I can think to check are the standard queries you do on rpm's but with a -p option and specify the filename that was written. For example, you can run rpm -qpl quagga-0.96.4.s390.rpm (or whatever the filename) and make sure all the files you think should be there are... Other biggees are rpm -qp --scripts and rpm -qpR, etc. There's a bunch of query options listed in the man pages. There's also rpm --checksig too, I suppose, but of course that should succeed. ~ 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
creating initrd /boot/initrd for kernel /boot/kernel/image (version 2.4.21-83-default) (s390) dasd_mod: failed to add module /lib/modules/2.4.21-83- default/kernel/drivers/s3 90/block/dasd_mod.o initrd too small Run zipl now to update the IPL record! how do I make it bigger? How much freespace do you have for files placed in /var/tmp/? Is it possible you are about full? Looking at /sbin/mkinitrd, it looks like SuSE first makes one initrd (20480k), populates it, then figures out how much it REALLY needs. It creates a second initrd of the really needed size, then copies everything over. Your error is during that last copy part, indicating that the second initrd really isn't big enough. Either mkinitrd's img_size calculation on line 1058 is wrong, or you run out of room while creating the new one. At line at 1061 which is: dd if=/dev/zero of=$tmp_initrd_small bs=1k count=$img_size 2/dev/null Can you remove the 2/dev/null portion of that, run mkinitrd again and see if you get any No space left on device errors? ~ 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
At line at 1061 which is: dd if=/dev/zero of=$tmp_initrd_small bs=1k count=$img_size 2/dev/null Can you remove the 2/dev/null portion of that, run mkinitrd again and see if you get any No space left on device errors? I did as you suggested, but I don't get any additional messages, it's the exact same thing. That's strange. You should have at least seen something kind of like: 20629+0 records in 20629+0 records out somewhere after 'creating initrd /boot/initrd for kernel /boot/kernel/image' but before 'dasd_mod: failed to add module /lib/modules/2.4.21-83-default/kernel/drivers/s3 90/block/dasd_mod.o initrd too small' Does a which mkinitrd return /sbin/mkinitrd? At this point I can only suggest you do a bash -x mkinitrd and post the output in order to figure out what codepath your mkinitrd script is taking. I mean, you could try upping the size of the initial initrd (look for # maximum initrd size and image_blocks=20480), but the fact that you get zero output from the second dd though the initrd too small error clearly comes after it makes me wonder what is really going on... ~ 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
It looks like that messages is generated around line 837 in the mkinird, before your change. Ugh, my find had wrapped back to the beginning without me realizing. Okay, on line 844 tar -C $root_dir -cf - $x 2/dev/null | tar -C $tmp_mnt -xpf - 2/dev/null you're getting a rc 127. It's as if there is no tar command in your path. If you have one (preferably in /bin/tar), then try taking out the 2/dev/null's on that line and run it again and see what tar complains about. Pretty sure tar exits with 0, 1, or 2 though, so it really seems like the shell can't find tar. + x=lib/modules/2.4.21-83-default/kernel/drivers/s390/block/dasd_mod.o + '[' lib/modules/2.4.21-83-default/kernel/drivers/s390/block/dasd_mod.o ']' + tar -C / -cf - lib/modules/2.4.21-83- default/kernel/drivers/s390/block/dasd_mo d.o + tar -C /var/tmp/mnt3883 -xpf - + '[' 127 '!=' 0 ']' + echo 'dasd_mod: failed to add module /lib/modules/2.4.21-83- --- 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
chandev_initdevice detected duplicate devicename eth0
I'm trying to be able to toggle an additional IP address between two guests (qdio GLAN, VM's TCPIP is the router). VM 4.3, SLES 8 SP3 guests. Our VM guy added the additional three devices required for QDIO on one guest, and then a different three on another. I could have one of the guests listen to its second interface with something like: ifconfig eth1 10.176.137.3 mtu 1400 netmask 255.255.255.128 broadcast 10.176.137.127 and then bring it down with ifconfig eth1 down. It's dmesg is: qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.337.4.16 $/$Revision: 1.113.4.5 $/$Revision: 1.42.4.3 $:IPv6:VLAN) qeth: allocated 0 spare buffers qeth: Trying to use card with devnos 0x740/0x741/0x742 qeth: Device 0x740/0x741/0x742 is a Guest LAN QDIO card (level: V434) with link type Gigabit Eth (portname: VMGLAN) qeth: VLAN not supported on eth1 qeth: IPv6 not supported on eth1 qeth: Broadcast packets will not be echoed back on eth1. qeth: Trying to use card with devnos 0x71C/0x71D/0x71E qeth: Device 0x71C/0x71D/0x71E is a Guest LAN QDIO card (level: V434) with link type Gigabit Eth (portname: VMGLAN) qeth: VLAN not supported on eth0 qeth: IPv6 not supported on eth0 qeth: Broadcast packets will not be echoed back on eth0. eth0: no IPv6 routers present eth1: no IPv6 routers present eth1: no IPv6 routers present eth1: no IPv6 routers present eth1: no IPv6 routers present I enabled/disabled eth1 a few times here. The other server, however, gets this error: # ifconfig eth1 10.176.137.3 mtu 1400 netmask 255.255.255.128 broadcast 10.176.137.127 SIOCSIFADDR: No such device eth1: unknown interface: No such device SIOCSIFMTU: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device eth1: unknown interface: No such device I also noticed the detected duplicate devicename eth0 error in dmesg, and no messages about eth1: qdio: loading QDIO base support version 2 ($Revision: 1.145.4.1 $/$Revision: 1.66.4.1 $) IPsec Security Association Database (SADB): initialized. IPsec Security Policy Database (SPD): initialized. IPsec PF_KEY V2: initialized IPv6 v0.8 (usagi-cvs/IPsec6 based StS) for NET4.0 IPv6 over IPv4 tunneling driver qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.337.4.16 $/$Revision: 1.113.4.5 $/$Revision: 1.42.4.3 $:IPv6:VLAN) qeth: allocated 0 spare buffers qeth: Trying to use card with devnos 0x73C/0x73D/0x73E qeth: Device 0x73C/0x73D/0x73E is a Guest LAN QDIO card (level: V434) with link type Gigabit Eth (portname: VMGLAN) qeth: VLAN not supported on eth0 qeth: IPv6 not supported on eth0 qeth: Broadcast packets will not be echoed back on eth0. qeth: Trying to use card with devnos 0x710/0x711/0x712 qeth: Device 0x710/0x711/0x712 is a Guest LAN QDIO card (level: V434) with link type Gigabit Eth (portname: VMGLAN) chandev_initdevice detected duplicate devicename eth0 eth0: no IPv6 routers present Any ideas why it works for one and not the other? Both servers only have ifcfg-eth0 and ifcfg-lo config files in /etc/sysconfig/network. They both have: alias eth0 qeth alias eth1 qeth at the bottom of modules.conf. The files are exactly the same on both servers. And they both look OK for chandev.conf: The one that works: noauto;qeth0,0x071c,0x071d,0x071e;add_parms,0x10,0x071c,0x071e,portname: VMGLAN noauto;qeth1,0x0740,0x0741,0x0742;add_parms,0x10,0x0740,0x0742,portname: VMGLAN The one that doesn't work: noauto;qeth0,0x0710,0x0711,0x0712;add_parms,0x10,0x0710,0x0712,portname: VMGLAN noauto;qeth0,0x073c,0x073d,0x073e;add_parms,0x10,0x073c,0x073e,portname: VMGLAN Any ideas what might be causing the problem? Also, any idea why I get the Broadcast packets will not be echoed back on eth0. messages? Thanks for any help, ~ 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: chandev_initdevice detected duplicate devicename eth0
The one that doesn't work: noauto;qeth0,0x0710,0x0711,0x0712;add_parms,0x10,0x0710,0x0712,portname: VMGLAN noauto;qeth0,0x073c,0x073d,0x073e;add_parms,0x10,0x073c,0x073e,portname: VMGLAN Looks like a typo ;) The second one should be qeth1. D'oh, thank you! If you use qeth0 for both devices, they'll both get the interface number 0. It would work if one were, for example, eth0 and the other tr0... Interesting. Best regards / Mit freundlichen Gruessen Thank you again Cornelia, ~ 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: Quagga Installation Questions
I am seeing a build requirement for package tetex. This is not part of the SuSe SLES8 distribution. I have been unable to determine if tetex is really necessary or not. Should I install tetex as well? Any ideas and opinions are welcomed. Thanks. There are te... and ...tex type packages available on your supplementary cd, including tetex-beta.20020207-93. After it's installed, you should probably go through the motions of YaST2's SuSE config. I don't remember if it was one of the te/tex type packages or just docbook, but even after installing them for a build, the doc portion still failed with errors. Later after SuSE config ran, however, everything just worked. At any rate, the tetex would only be required to build the src.rpm into the appropriate arch.rpms. It won't be a run-time/install dependency. Meaning if you have one big image that you do your building on, once the rpm is built you can install it on other images without tetex without any problem. An alternative is to look at how the .spec is constructed. The author might have been nice enough to let you easily disable building the documentation that relies on tetex. If not, it gets more complicated, and is usually easier to just install the package than hunting through the configure/Makefile etc. ~ 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 Print Config Problem - Insufficient access rights to connect
I am getting this error on a new Samba (SLES8) printer config... (first time we're trying samba at this account) What version of Samba? When trying to connect to the linux574 printer You do not sufficient access rights to your machine to connect to the selected printer Maybe one of the below will help: http://lists.samba.org/archive/samba-ntdom/2001-April/019337.html http://www.jsiinc.com/SUBM/tip6100/rh6156.htm http://support.microsoft.com/?kbid=149913 http://support.microsoft.com/?kbid=259937 I think I have file permissions set correctly also. ANY IDEAS?? My smb.conf: [printers] comment = All Printers path = /var/spool/samba write list = @ntadmin root itnry create mask = 0600 guest ok = Yes printable = Yes browseable = No [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 [linux574] comment = IBM InfoPrint 1352 path = /var/spool/samba guest account = itnry write list = @ntadmin root itnry read only = No create mask = 0600 guest ok = Yes printable = Yes printer name = linux574 Is that your complete smb.conf? Do you not have a [global] section? Did testparm seem to think everything okay? If the above links don't do it for you, more information (like your [global] section... specifically security = ??) in smb.conf, and how you are connecting, could help. Sounds like the problem is at the client side, though, not necessarily samba config. ~ 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: Format disk and mount FS : lost space
Carsten Otte wrote: Daniel wrote: The larger the number of cyls for the device, the worse the ratio gets :(. That's not true: CDL uses track0 and track1 for internal purposes, the rest (number of 4k blocks that fit on a track multiplied with amount of tracks) is available for partitions. For people who do not like that overhead can just use LDL which only uses 2 blocks (8 kilobytes) as overhead. Sorry to be unclear, I was referring to the 49152 bytes/track (12 * 4K) vs. the true 56664 bytes/track for emulated/real ECKD devices, not the CDL/partition overhead. I said, The CDL, partition, filesystem/journal overhead is really quite tiny in comparison. The whole comment about the ratio getting worse as volume size increases was due to: A1. CDL/partition overhead is fixed, no increase in overhead. A2. Journal overhead is fixed, unless you use a larger journal. A3. Filesystem overhead may vary with the data, but again tiny compared to... B1. A constant lost of 112,680 bytes for every ECKD cylinder (13.25%), which is what I was sniveling about. ~ 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: Format disk and mount FS : lost space
We have formated a mini disk of 285 Cylinders with : dasdfmt -b 4096 -n 0104 dev2:/mnt# less /proc/dasd/devices 0104(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 51300 blocks, 200 MB Going over the numbers, the overhead from dasdfmt is startling. At 849,960 bytes a cylinder, your 285 cyls should yield 242,238,600 bytes. Yet formatted at 12 4k blocks per track, you only get 4096 * 51300 = 210,124,800. Right there, that's 13.26% out the window immediately. The CDL, partition, filesystem/journal overhead is really quite tiny in comparison. The larger the number of cyls for the device, the worse the ratio gets :(. From Neale Ferguson's SCSI on Linux for zSeries presentation, it looks like he doesn't have to worry about this :). ~ 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: Problems with CUPS/SAMBA config (print drivers)
Hi Dave, 1. I ran the cupsaddsmb command and I see that it created InfoPrint_1125.PPD, which looks right for my Infoprint 1125 printer. What's in /var/lib/samba/drivers/, /var/lib/samba/drivers/W32X86/, and /var/lib/samba/drivers/W32X86/2 or /var/lib/samba/drivers/W32X86/3? Not sure why we're using W32X86 (how does that relate?) Drivers for windows 95 and higher clients on x86. Problem:When I go to add the printer to my W2K client (and download the driver)... I get The server on which the 'Infoprint_1125' printer resides does not have the correct printer driver installed, if you want to install the driver on your local computer, click OK Then OK Here you should click No or Cancel or whatever the other option is, not OK. Clicking OK would try to install the driver locally instead of on the server. Then Type the file where the file is located and it's looking for an .INF file...not a *.PPD ??? .inf is to install the windows client driver locally. When I added the CUPS printer with the lpadmin command I did not know which *.ppd.gz to use, so I just picked the Infoprint_12-gimp-print.ppd.gz maybe that is related to my problem? You probably don't want to use the gimp drivers, but whatever you select there will not affect your windows clients which would be printing in RAW. This might affect things like the banner/cover page though, and print jobs initiated from linux. 2. Also the UPLOAD procedure did not work for me..that is why I used cupsaddsmb. On the foid where is reads There should be no driver that was true...but the New Driver button was grayed out and unselectable. Is the user you are connecting to samba with configured as a printer admin in /etc/samba/smb.conf? TIA, Good luck, ~ 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: Problems Compiling Samba 3.0.2a on SLES8 SP3
In file included from /usr/include/asm/statfs.h:6, from /usr/include/linux/vfs.h:4, from /usr/include/linux/fs.h:13, from /usr/include/linux/capability.h:17, from /usr/include/sys/capability.h:24, from include/includes.h:355, from dynconfig.c:21: /usr/include/asm-s390/statfs.h:20: redefinition of `struct statfs' Perhaps not the correct fix, but I worked around this by doing a: #ifndef _SYS_STATFS_H #endif around the struct statfs in /usr/include/asm-s390/statfs.h ~ 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
linux idle ticks under vm
We have a few linux servers with kernel.hz_timer = 0 that run under z/VM. I'm not sure how that patch factors into things below. I know the linux CPU numbers are relative to the CPU z/VM gives the dispatched guest, but how about idle ticks/jiffies from the linux perspective? The VM accounting records show that we usually have CPU to spare, and except during things like compiles, the guests are usually more idle than not from the linux perspective. So if the VM records show that a guest used 10% of the total CPU, and a before/after of /proc/stat shows that half of the ticks were spent in the idle task, did the guest truly only need 5%? As more guests use CPU, I'd expect that guest's usage to drop below 10% from z/VM's perspective, and the idle jiffies to drop from linux's perspective, but the user/nice/system numbers would not change much assuming similar work was being done, and we aren't always running at 100%. Does that sound about right? ~ 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
