On Monday 23 October 2006 02:40, Roy Marples wrote:
> On Sunday 22 October 2006 13:24, Mike Frysinger wrote:
> > thus RC_STRICT_NET_CHECKING=lo gave me the perfect behavior
>
> And by default you'll get that behaviour.
i'll take your word n it ... if it doesnt behave this way, i know where to
fin
On Sunday 22 October 2006 13:24, Mike Frysinger wrote:
> all use this:
> > lo - net is up if lo is up
> > Just have net.lo in the boot runlevel - it should always be there anyway.
>
> so you're saying if net.lo is in the boot runlevel, and i put say net.eth0
> [wired] and net.eth1 [wireless] into m
On Sunday 22 October 2006 07:52, Roy Marples wrote:
> OK, from my persepective we had RC_STRICT_NET_CHECKING because we couldn't
> previously handle multiple provides. Here's how the new way translates.
i use it because i want to disable most net based requirements ... my machines
all use this:
Roy Marples ha scritto:
[...]
>
> Seriously though, poeple should only use baselayout features that found in
> stable baselyout. It took over a year for 1.12 to finally go stable - even
> then there were quite a few hiccups. 1.13 should be no different as we now
> have direct support for FreeBS
Roy Marples ha scritto:
> On Sunday 22 October 2006 19:47, Luca Longinotti wrote:
>> Hmmm from how I understood it, basically you cannot provide something
>> that already exists (so if there is a mysql init script, you can't
>> provide mysql in another init-script), but you can make up some fancy
>
I hate replying to myself as it's the first sign of madness, but ...
On Sunday 22 October 2006 12:52, Roy Marples wrote:
> no - net is up if any interface except for lo is up
> This is the tricky one as we have effectively lost it
Not exactly true. If we stop net.lo from providing net then we reg
On Sunday 22 October 2006 19:38, Francesco Riosa wrote:
> Roy Marples ha scritto:
> > On Sunday 22 October 2006 13:01, Francesco Riosa wrote:
> >> This is a nice thing for mysql since it can use two init scripts "mysql"
> >> and "mysqlmanager". Both provide "mysql".
> >
> > You cannot provide somet
On Sunday 22 October 2006 19:47, Luca Longinotti wrote:
> Hmmm from how I understood it, basically you cannot provide something
> that already exists (so if there is a mysql init script, you can't
> provide mysql in another init-script), but you can make up some fancy
> name to do that?
> Fex: dev-
Francesco Riosa wrote:
> because if "mysqlmanager" provide mysql _now_ all the < baselayout-1.13
> versions will complain loudly, that's because "provide mysql" is
> commented out in the current init.d/mysqlmanager::depend() ;)
Hmmm from how I understood it, basically you cannot provide something
Roy Marples ha scritto:
> On Sunday 22 October 2006 13:01, Francesco Riosa wrote:
>> This is a nice thing for mysql since it can use two init scripts "mysql"
>> and "mysqlmanager". Both provide "mysql".
>
> You cannot provide something that already exists, so msqld will have to
> provide mysql.
On Sunday 22 October 2006 13:01, Francesco Riosa wrote:
> This is a nice thing for mysql since it can use two init scripts "mysql"
> and "mysqlmanager". Both provide "mysql".
You cannot provide something that already exists, so msqld will have to
provide mysql.
> Is there an environment variable
Roy Marples ha scritto:
> Hi List
>
[...]
>
> baselayout-1.13 now handles multiple provides. That means that you have can 3
> or more services that provide "logger" and baselayout will pick the right one
> based on what's running, then what's run the runlevel and finally
> alphabetical order.
On Sunday 22 October 2006 03:08, Mike Frysinger wrote:
> On Saturday 21 October 2006 10:05, Roy Marples wrote:
> > baselayout-1.13 now handles multiple provides. That means that you have
> > can 3 or more services that provide "logger" and baselayout will pick the
> > right one based on what's runn
On Saturday 21 October 2006 10:05, Roy Marples wrote:
> baselayout-1.13 now handles multiple provides. That means that you have can
> 3 or more services that provide "logger" and baselayout will pick the right
> one based on what's running, then what's run the runlevel and finally
> alphabetical or
On 10/21/06, Roy Marples <[EMAIL PROTECTED]> wrote:
RC_STRICT_NET_CHECKING is used in the init script depdency process, and quite
frankly I'd like to punt it and replace it with ... rc-update! Yes,
just put the init scripts that "net" should provide in your runlevel. boot
contains net.lo
Hi List
Whilst working on a new C program to work out init script dependencies (99%
done and working and very very fast) it suddenly struct me as to why we still
have RC_STRICT_NET_CHECKING (see conf.d/rc for what it does).
baselayout-1.13 now handles multiple provides. That means that you have
16 matches
Mail list logo
