I don't think you want to have a local lock file. I imagine it's there to
prevent corruption when used from multiple processes.

Assuming your student are in the same group, try this:

chmod g+w "${STACK_ROOT}/stack.sqlite3.pantry-write-lock"
chmod g+w "${STACK_ROOT}/pantry/pantry.sqlite3.pantry-write-lock"
echo 'allow-different-user: true' >>"${STACK_ROOT}/config.yaml"


On Fri, 25 Oct 2019 at 05:34, Ben MacAdam <benmaca...@gmail.com> wrote:

> There seems to be an issue trying this out on my own machine - the
> students seem to need write access to stack.sqlite3.pantry-write-lock
>
> >/Users/ROOT_ACCOUNT/.stack/pantry/pantry.sqlite3.pantry-write-lock:
> openFd: permission denied (Permission denied)
>
> Is there any way to have a local lock file?
>
>
> On Wednesday, 23 October 2019 16:18:11 UTC-6, Steven Shaw wrote:
>>
>> Assuming your students are logged into the same machine you should be
>> able to use the STACK_ROOT environment variable
>> <https://docs.haskellstack.org/en/stable/GUIDE/#setting-stack-root-location>.
>> You should be able to use OS permissions to prevent write access to a
>> particular user.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "haskell-stack" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to haskell-stack+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/haskell-stack/efb09866-399c-4fb7-ad74-47d075f93f06%40googlegroups.com
> <https://groups.google.com/d/msgid/haskell-stack/efb09866-399c-4fb7-ad74-47d075f93f06%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"haskell-stack" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haskell-stack+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/haskell-stack/CAMP6nJxz%2BtggBEUEViRonmZgKykm0y62Mdb7B8FLsVue3e831A%40mail.gmail.com.

Reply via email to