We're reproducing the same error on our 1.1.2 copies. Has anyone filed
a ticket for this yet as per Nicolas' suggestion? If so, please post
URL. If not, I'll open one tomorrow (i'm late for dinner now :-)

--peter

On Sep 20, 4:24 am, Cristiano <[EMAIL PROTECTED]> wrote:
> Yeah, that's not really a solution. I need my production app to be
> able to be disabled for during upgrades.
>
> On Sep 19, 1:28 am, [EMAIL PROTECTED] wrote:
>
> > Cristiano wrote:
> > > I had a quick back and forward between symfony 1.1.1 and 1.1.2 and it
> > > is definitely a 1.1.2 issue. Trying to figure out at the moment what
> > > line is causing the issue. I made a diff of the changes between 1.1.1
> > > and 1.1.2 in the /lib/task/cache/sfCacheClearTask.class.php file but
> > > can't figure out what is causing it yet.
>
> > > On Sep 18, 8:46 pm, Cristiano <[EMAIL PROTECTED]> wrote:
> > >> I have exactly this same issue.
>
> > >> On Sep 18, 6:23 pm, jukea <[EMAIL PROTECTED]> wrote:
>
> > >>> hi,
> > >>> symfony cc locks each environement before clearing the files.
> > >>> For me, the task seemed broken. So, after tracking the bug, it turns
> > >>> out that my symfony cc locks the CLI env too (is this normal?), and
> > >>> thus quits with an unavailable page outputed directly in the
> > >>> console...
> > >>> so in other terms, it locks itself in !
> > >>> anyone has any idea why ?
>
> > I updated a site to 1.1.2 this morning and had the same problem. In my
> > case, simply setting 'check lock' to off (the symfony default) in
> > settings.yml prevented this. I haven't had a chance to chase it down any
> > further than that.
>
> > HTH,
>
> > GM
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to