[
http://dev.sourcefabric.org/browse/LS-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29649#action_29649
]
Samuel Mimram commented on LS-646:
----------------------------------
Well I think I investigated this quite in details (as explained above) and I
don't see any other solution... The problem is that the default parameter for
opening files in read-only is not propagated to high-level functions. A
temporary solution would be to apply the following patch (untested...) to taglib
diff --git a/taglib/toolkit/tfilestream.h b/taglib/toolkit/tfilestream.h
index fa113b7..397ed26 100644
--- a/taglib/toolkit/tfilestream.h
+++ b/taglib/toolkit/tfilestream.h
@@ -52,7 +52,7 @@ namespace TagLib {
* Construct a File object and opens the \a file. \a file should be a
* be a C-string in the local file system encoding.
*/
- FileStream(FileName file, bool openReadOnly = false);
+ FileStream(FileName file, bool openReadOnly = true);
/*!
* Destroys this FileStream instance.
> Have taglib open files in read-only mode
> ----------------------------------------
>
> Key: LS-646
> URL: http://dev.sourcefabric.org/browse/LS-646
> Project: Liquidsoap
> Issue Type: Bug
> Components: ocaml-taglib
> Reporter: Samuel Mimram
>
> Martin reported this bug on the ML:
> I have the following command line :
> liquidsoap -c "output.dummy(audio_to_stereo(single('avicii.mp3')))"
> and simple c program that uses inotify to monitor accesses to a directory
> (available here:
> http://darkeside.blogspot.ca/2007/12/linux-inotify-example.html)
> This is all a very simple test environment set up to recreate what we are
> currently experiencing.
> So whenever I run the above Liquidsoap command, the inotify program reports
> the file was opened in read/write mode. If I take away write permissions on
> this file, then Liquidsoap opens it in read mode.
> This opening in write mode is a problem for us, because we are listening for
> these events with our media-monitor to ensure the file's metadata are in sync
> with Airtime's database, and introduces a few complications
> (http://dev.sourcefabric.org/browse/CC-4343).
> Is there a reason for this behaviour, or can we change it?
> Martin
> P.S. Sorry for the possibly overly-verbose email :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://dev.sourcefabric.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
_______________________________________________
Savonet-devl mailing list
Savonet-devl@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-devl
