On Friday, 10/03/2014 at 05:34 EDT, "Smith, Ann (CTO Service Delivery)" <ann.sm...@thehartford.com> wrote: > But it is useful in DR network where the network is being redesigned by > customer's network folks. > The mainframe linux servers may be up before the LDAP servers are fully > functional (at least those without san). > The ldap client processes can time out. The local id is used to restart them > after LDAP available. > LDAP's not on z.
Why not just use the CMS LDAP client to discover when LDAP is up, and then kick off the startup? Works both at home and away. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems & Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott ---------------------------------------------------------------------- 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/
