PasTim wrote: 
> My understanding from a rather large number of posts is that ffmpeg can
> even be run by admin from a command line, not just root.  Is that
> wrong?
> 
> If ordinary admin can run it OK, then:
> 
> - is there an environment variable used or set by LMS that could also be
> affecting ffmpeg or one of the libraries it uses? 
> - is there a resource that LMS is reserving for its sole use?
> - is there an unexpected resource that ffmpeg tries to reserve, even if
> not actually used, that LMS uses?
> - can any more diagnostics be got out of ffmpeg or its libraries?
> 
> I know, scraping the barrel for ideas, but ????

Klammer (armada370 based Synology) is the only Synology with the problem
persisting. ffmpeg doesn't work when run from a shell prompt under
userid admin but works nder user id root. This is not the case for other
Synology NASs.  ffmpeg (owned by user root) when permissions set to "+s"
will run from a shell prompt when run under user admin but not when run
as part of LMS.

Problem is I can't test all the questions you are asking as I don't have
a NAS and Klammer doesn't have the skill to answer the questions you are
asking.   So all we can do is try to provoke the error message on a
system where ffmpeg works and then see can it be undone on Klammer's
system. As an alternative,  I have gone through the ffmpeg code to see
where the error is produced - unfortunately it is in a lot (but finite)
of places.


------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=103158

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to