If you do need multiple operators, you can always use muliple jobs.
One with all the ORs and another with the ANDs including it.
Bug fix? Err, it's a bit of a fundamental design flaw. That'll be for
lynx ;)
Sent from my iPhone
On 10 Oct 2009, at 20:20, Steve Langasek
<email address hidden> wrote:
> "using one type of operator" - well, this is probably doable; the only
> and+or case we have currently is gssd, which wants local-filesystems
> and
> (portmap or mount TYPE=nfs4 OPTIONS=sec=*krb5*), and portmap implies
> local-filesystems at boot time. It's not 100% correct, but it
> should be
> usable. Will test and report back.
>
> Prognosis of fixing the upstart bug?
>
> --
> NFSv4 automounting completely broken?
> https://bugs.launchpad.net/bugs/447654
> You received this bug notification because you are subscribed to
> mountall in ubuntu.
If you do need multiple operators, you can always use muliple jobs.
One with all the ORs and another with the ANDs including it.
Bug fix? Err, it's a bit of a fundamental design flaw. That'll be for
lynx ;)
Sent from my iPhone
On 10 Oct 2009, at 20:20, Steve Langasek
<email address hidden> wrote:
> "using one type of operator" - well, this is probably doable; the only sec=*krb5* ), and portmap implies /bugs.launchpad .net/bugs/ 447654
> and+or case we have currently is gssd, which wants local-filesystems
> and
> (portmap or mount TYPE=nfs4 OPTIONS=
> local-filesystems at boot time. It's not 100% correct, but it
> should be
> usable. Will test and report back.
>
> Prognosis of fixing the upstart bug?
>
> --
> NFSv4 automounting completely broken?
> https:/
> You received this bug notification because you are subscribed to
> mountall in ubuntu.