On Thu, 28 Jun 2007 15:44:44 +0100
Alan Maguire <[EMAIL PROTECTED]> wrote:

> hi Michael
> 
> quick question - should there also be a direct
> dependency on rpc/bind for cases where nis
> is not used as the name service for rpc lookups?
> (inetd-upgrade will inherit a dependency
> on rpc/bind via nis/client, but not if other name
> services are enabled as far as i can see). thanks!

This is part of the problem that Jim is talking about.  I don't beleive
there is tight coupling between how nsswitch is configured and what
services are enabled.

I noticed that Duckwater (http://opensolaris.org/os/project/duckwater/)
put some bits out yesterday so I should go see where there design is
headed.  I havn't paid as much attention to that project as I should
have in the recent months.

                        mph

> 
> alan
> 
> Michael Hunter wrote:
> > http://bugs.opensolaris.org/view_bug.do?bug_id=6197413
> > 6197413 network/inetd-upgrade service times out
> >
> > The evaluation of this bug reduces it down to the need for
> > inetd-upgrade to have a dependency on milestone/name-services.
> >
> > The current file:
> >
> > http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/cmd-inet/usr.lib/inetd/inetd-upgrade.xml
> >
> > Diffs after my signature.
> >
> >                     mph
> >
> > Index: usr/src/cmd/cmd-inet/usr.lib/inetd/inetd-upgrade.xml
> > *** /tank/ws/nvclone/usr/src/cmd/cmd-inet/usr.lib/inetd/inetd-upgrade.xml   
> >     Mon Apr  2 17:27:54 2007
> > --- /tank/ws/bug/usr/src/cmd/cmd-inet/usr.lib/inetd/inetd-upgrade.xml   Thu 
> > Jun 21 00:10:53 2007
> > ***************
> > *** 1,15 ****
> >   <?xml version="1.0"?>
> >   <!DOCTYPE service_bundle SYSTEM 
> > "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
> >   <!--
> > !  Copyright 2005 Sun Microsystems, Inc.  All rights reserved.
> >    Use is subject to license terms.
> >   
> >    CDDL HEADER START
> >   
> >    The contents of this file are subject to the terms of the
> > !  Common Development and Distribution License, Version 1.0 only
> > !  (the "License").  You may not use this file except in compliance
> > !  with the License.
> >   
> >    You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
> >    or http://www.opensolaris.org/os/licensing.
> > --- 1,14 ----
> >   <?xml version="1.0"?>
> >   <!DOCTYPE service_bundle SYSTEM 
> > "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
> >   <!--
> > !  Copyright 2007 Sun Microsystems, Inc.  All rights reserved.
> >    Use is subject to license terms.
> >   
> >    CDDL HEADER START
> >   
> >    The contents of this file are subject to the terms of the
> > !  Common Development and Distribution License (the "License").
> > !  You may not use this file except in compliance with the License.
> >   
> >    You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
> >    or http://www.opensolaris.org/os/licensing.
> > ***************
> > *** 24,30 ****
> >   
> >    CDDL HEADER END
> >   
> > !       ident   "@(#)inetd-upgrade.xml  1.5     05/06/08 SMI"
> >   
> >         NOTE:  This service manifest is not editable; its contents will
> >         be overwritten by package or patch operations, including
> > --- 23,29 ----
> >   
> >    CDDL HEADER END
> >   
> > !       ident   "@(#)inetd-upgrade.xml  1.6     07/06/21 SMI"
> >   
> >         NOTE:  This service manifest is not editable; its contents will
> >         be overwritten by package or patch operations, including
> > ***************
> > *** 62,67 ****
> > --- 61,74 ----
> >                 <service_fmri value='svc:/system/filesystem/local'/>
> >         </dependency>
> >   
> > +       <dependency
> > +               name='name-services'
> > +               grouping='require_all'
> > +               restart_on='none'
> > +               type='service'>
> > +               <service_fmri value='svc:/milestone/name-services'/>
> > +       </dependency>
> > + 
> >         <exec_method
> >                 type='method'
> >                 name='stop'
> > _______________________________________________
> > networking-discuss mailing list
> > [email protected]
> >   
> 
> _______________________________________________
> networking-discuss mailing list
> [email protected]
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to