Re: VDISK-SWAP-SWAPGEN ???
Make sure that, once you have manually gotten everything to work, you run mkinird and zipl to create the new initrd image containing the parameters to load the diag and fba drivers. This should make the next boot a bit... Smoother. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 7/31/08 4:44 PM, Huegel, Thomas [EMAIL PROTECTED] wrote: Thanks Adam.. That makes total sense. BTW as I was messing around I see I do have dasd_diag_mod, so I guess I could use the 'perfered' DIAG format in SWAPGEN and then swap to dasdb1 .. This LINUX stuff is going to make the rest of my hair turn grey.. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Adam Thornton Sent: Thursday, July 31, 2008 4:30 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: VDISK-SWAP-SWAPGEN ??? On Jul 31, 2008, at 3:59 PM, Huegel, Thomas wrote: Yes I have dasd_fba_mod loaded, I don't know about dasd_diag_mod.. Here are some more messages... swapon -a Unable to find swap-space signature swapon: /dev/dasdb1: Invalid argument linmstr:~ # Jul 31 15:54:23 linmstr kernel: Unable to find swap- space signature swapon /dev/dasdb swapon /dev/dasdb Adding 49992k swap on /dev/dasdb. Priority:-1 extents:1 Jul 31 15:55:19 linmstr kernel: Adding 49992k swap on /dev/dasdb. Priority:-1 extents:1 Hmmm, OK. So the swapspace signature IS on /dev/dasdb, and it swapped on OK. So I think what's going on is that, for some reason, it's initially trying to swap on before dasd_fba_mod is loaded. So you probably need to build the ramdisk again with dasd_fba_mod in it, or you can just do a late-in-the-boot-process swapon -a once the device driver is loaded. Adam -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- 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: NFS server and mapping UID/GID from z/OS USS
I think you could use the squash parameter. I use something like this squash_all,anonuid=SOMEID,anongid=SOMEID Cavet is you can only map n - 1 not n - n user relations. Christian Langer John D Randles schrieb am 31.07.2008 20:03: Hi there is there an easy way to map USS UID/GID from z/OS USS to Linux accross an NFS mount point ? In older versions of NFS there was a map_static=map.file parameter where you could build your own static mapping table, but in NFSv4 it seems to have gone. We dont have a common LDAP or NIIS server for both systems at this point. Any help greatly appreciated. John Randles email: [EMAIL PROTECTED] American Express made the following annotations on Thu Jul 31 2008 11:03:24 -- This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you. American Express a ajouté le commentaire suivant le Thu Jul 31 2008 11:03:24 Ce courrier et toute pièce jointe qu'il contient sont réservés au seul destinataire indiqué et peuvent renfermer des renseignements confidentiels et privilégiés. Si vous n'êtes pas le destinataire prévu, toute divulgation, duplication, utilisation ou distribution du courrier ou de toute pièce jointe est interdite. Si vous avez reçu cette communication par erreur, veuillez nous en aviser par courrier et détruire immédiatement le courrier et les pièces jointes. Merci. ** --- -- 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 -- |Zentrum für Informationsverarbeitung | und Informationstechnik |Haus I Raum 339 |An der Kueppe 2 |53225 Bonn |Mail: [EMAIL PROTECTED] |Tel: 0228 99680 5199 -- 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 signature.asc Description: OpenPGP digital signature
Re: VDISK-SWAP-SWAPGEN ???
The copy I have was updated on 4/16/08. It doesn't appear to have been drastic changes, though. The current version of SWAPGEN is available from http://download.sinenomine.net/swapgen It was last updated on 16 May, 2008. I'm almost finished with the internationalized version, and I need to update it for OpenSolaris sometime soon, but that's where you can find the definitive version. -- db -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Problem with sendmail (and mailx)
We have several RHEL 4.5 servers running Oracle. Each is a clone of the original. However I discovered that we can only send email from two (using the mailx command). I am not an expert on sendmail, however I have looked at every configuration file I can find to see if I can locate a difference between the servers that work and the servers that do not work and have come up empty. I looked at sendmail.cf and submit.cf, and their respective *.mc files, with no differences found. In the /etc/log/maillog file I found the following between servers (working and not working): Working: Jul 31 14:58:59 zn023 sendmail[30613]: m6VIwxY2030613: [EMAIL PROTECTED], ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32986, relay=mailhost [10.159.4.16], dsn=2.0.0, stat=Sent (Message accepted for delivery) Fail to send: Jul 31 14:48:50 zn019 sendmail[27586]: m6VImo9Z027586: [EMAIL PROTECTED], ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32985, relay=mailhost [10.159.4.16], dsn=5.0.0, stat=Service unavailable Does anyone have any insight to this and how/where the DSN values (Delivery Status Notification) is set, where I may look to find the root of this fail to send or any suggestions. James Chaplin Systems Programmer, MVS, zVM zLinux Base Technologies, Inc (703) 921-6220 -- 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: Problem with sendmail (and mailx)
Check the /etc/mail/local-host-names etc/hosts.allow etc/host.deny to see if zn019 is defined or not on the mailer 'Where ever you go - There you are!! ' Richard (Gaz) Gasiorowski Global Solutions Technology Principal Lead Infrastructure Architect 845-773-9243 Work 845-392-7889 Cell [EMAIL PROTECTED] Computer Sciences Corporation Registered Office: 3170 Fairview Park Drive, Falls Church, Virginia 22042, USA Registered in Nevada, USA No: C-489-59 - This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. - CHAPLIN, JAMES (CTR) [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 08/01/2008 05:01 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Problem with sendmail (and mailx) We have several RHEL 4.5 servers running Oracle. Each is a clone of the original. However I discovered that we can only send email from two (using the mailx command). I am not an expert on sendmail, however I have looked at every configuration file I can find to see if I can locate a difference between the servers that work and the servers that do not work and have come up empty. I looked at sendmail.cf and submit.cf, and their respective *.mc files, with no differences found. In the /etc/log/maillog file I found the following between servers (working and not working): Working: Jul 31 14:58:59 zn023 sendmail[30613]: m6VIwxY2030613: [EMAIL PROTECTED], ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32986, relay=mailhost [10.159.4.16], dsn=2.0.0, stat=Sent (Message accepted for delivery) Fail to send: Jul 31 14:48:50 zn019 sendmail[27586]: m6VImo9Z027586: [EMAIL PROTECTED], ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32985, relay=mailhost [10.159.4.16], dsn=5.0.0, stat=Service unavailable Does anyone have any insight to this and how/where the DSN values (Delivery Status Notification) is set, where I may look to find the root of this fail to send or any suggestions. James Chaplin Systems Programmer, MVS, zVM zLinux Base Technologies, Inc (703) 921-6220 -- 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: Problem with sendmail (and mailx)
You should've received a DSN message in the mailbox of the user who tried to send (root) from ds019, or (less likely) in the mailbox of the Postmaster user (on most linux systems, this is equivalent to root anyway). The actual error you're getting will be in that message, and will be much more valuable for troubleshooting this error than the entry in maillog. My first guess is that your relay server (10.159.4.16) is not configured to allow relaying from any of your servers but the two that are work. If it is also using sendmail, the file defining this is usually /etc/mail/relay-domains. The DSN message (in the user's mailbox) should tell you in more certain terms, though. ok r. -Original Message- From: CHAPLIN, JAMES (CTR) [mailto:[EMAIL PROTECTED] Sent: Friday, August 01, 2008 2:02 PM To: LINUX-390@VM.MARIST.EDU Subject: Problem with sendmail (and mailx) We have several RHEL 4.5 servers running Oracle. Each is a clone of the original. However I discovered that we can only send email from two (using the mailx command). I am not an expert on sendmail, however I have looked at every configuration file I can find to see if I can locate a difference between the servers that work and the servers that do not work and have come up empty. I looked at sendmail.cf and submit.cf, and their respective *.mc files, with no differences found. In the /etc/log/maillog file I found the following between servers (working and not working): Working: Jul 31 14:58:59 zn023 sendmail[30613]: m6VIwxY2030613: [EMAIL PROTECTED], ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32986, relay=mailhost [10.159.4.16], dsn=2.0.0, stat=Sent (Message accepted for delivery) Fail to send: Jul 31 14:48:50 zn019 sendmail[27586]: m6VImo9Z027586: [EMAIL PROTECTED], ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32985, relay=mailhost [10.159.4.16], dsn=5.0.0, stat=Service unavailable Does anyone have any insight to this and how/where the DSN values (Delivery Status Notification) is set, where I may look to find the root of this fail to send or any suggestions. James Chaplin Systems Programmer, MVS, zVM zLinux Base Technologies, Inc (703) 921-6220 -- 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: Problem with sendmail (and mailx)
You need to contact the MAIL ADMIN at 10.159.16.4- what cause the bounce back/reject. CHAPLIN, JAMES (CTR) [EMAIL PROTECTED] To sociates.dhs.gov LINUX-390@VM.MARIST.EDU Sent by: Linux cc on 390 Port [EMAIL PROTECTED] Subject IST.EDU Problem with sendmail (and mailx) 08/01/2008 05:01 PM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU We have several RHEL 4.5 servers running Oracle. Each is a clone of the original. However I discovered that we can only send email from two (using the mailx command). I am not an expert on sendmail, however I have looked at every configuration file I can find to see if I can locate a difference between the servers that work and the servers that do not work and have come up empty. I looked at sendmail.cf and submit.cf, and their respective *.mc files, with no differences found. In the /etc/log/maillog file I found the following between servers (working and not working): Working: Jul 31 14:58:59 zn023 sendmail[30613]: m6VIwxY2030613: [EMAIL PROTECTED], ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32986, relay=mailhost [10.159.4.16], dsn=2.0.0, stat=Sent (Message accepted for delivery) Fail to send: Jul 31 14:48:50 zn019 sendmail[27586]: m6VImo9Z027586: [EMAIL PROTECTED], ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32985, relay=mailhost [10.159.4.16], dsn=5.0.0, stat=Service unavailable Does anyone have any insight to this and how/where the DSN values (Delivery Status Notification) is set, where I may look to find the root of this fail to send or any suggestions. James Chaplin Systems Programmer, MVS, zVM zLinux Base Technologies, Inc (703) 921-6220 -- 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 Visit our website at http://www.nyse.com Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext, Inc. -- 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
