How long does one have to typically wait for an answer to a post? Tomorrow my message will have been up a week, and I've gotten no replies. It was about whether a file, while it was being written to, could subsequently be opened by another client for reading. I used a DVR with chasing play as an example. Didn't seem like that difficult of a question, but maybe it isn't geeky enough for some. (Or perhaps the answer is "No" and people are too embarrassed to admit Samba can't do it.)
On Wed, 2007-12-19 at 20:20 -0800, Michael Dykstra wrote:> How long does one have to typically wait for an answer to a post? > Tomorrow my message will have been up a week, and I've gotten no > replies. > It was about whether a file, while it was being written to, could > subsequently be opened by another client for reading. I used a DVR > with chasing play as an example. Didn't seem like that difficult of a > question, but maybe it isn't geeky enough for some. (Or perhaps the > answer is "No" and people are too embarrassed to admit Samba can't do > it.)Or perhaps the question is naive and the answer is: "it depends". Samba supports locking, so if the application that is writing to a file locks it then you may be out of luck.>From a protocol and server point of view, however, there is absolutelyno limitation on concurrent file reading/writing. Simo. -- Simo Sorce Samba Team GPL Compliance Officer <simo@samba.org> Senior Software Engineer at Red Hat Inc. <ssorce@redhat.com>
On 19 Dec 2007 at 20:20 Michael Dykstra fed the net:> How long does one have to typically wait for an answer to a post? > (...) Didn't seem like that > difficult of a question, but maybe it isn't geeky enough for some. > (Or perhaps the answer is "No" and people are too embarrassed to > admit Samba can't do it.)There is not a deterministic time ta get a reply: assume two hypothesis, H0: there is an answer and someone know what is, whether is positive or negative. H1: there is an answer, many people know that there is but is not able to give it. on H1 the reply should _not_ come: the only answer that could come is "i know it is possible but i do not know how" ... and this does not help a lot. on H0 the time is indefinite too: if the reply is not "easy" (or is even really easy, but only few people knopw, think of an obscure setting used only once every five years) you have to wait that your question is noticed by someone that know what is and have the time to reply it ! Once i got an answer on a program 18 months after i posted the question on the list (the reply was correct and useful, but in the meantime i had decided to use another application). -- Leonardo Boselli Nucleo Informatico e Telematico del Dipartimento Ingegneria Civile Universita` di Firenze , V. S. Marta 3 - I-50139 Firenze tel +39 0554796431 cell +39 3488605348 fax +39 055495333 http://www.dicea.unifi.it/~leo
On Dec 20, 2007 4:20 AM, Michael Dykstra <m.dykstra@yahoo.com> wrote:> How long does one have to typically wait for an answer to a post? > Tomorrow my message will have been up a week, and I've gotten no replies. > It was about whether a file, while it was being written to, could subsequently be opened by another client for reading. I used a DVR with chasing play as an example. Didn't seem like that difficult of a question, but maybe it isn't geeky enough for some. (Or perhaps the answer is "No" and people are too embarrassed to admit Samba can't do it.) > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba >Hello Michael, With open source projects, people involved are volunteering their time and skills. As such, people asking for help shouldn't really _demand_ for answers (of course, if you want to demand anything, there are plenty of companies giving Samba support - not free, I'm afraid). Please handle it gently :). If Samba can't do it, you'll be told upfront (no one will be embarassed). Cheers, Ari Constancio
Hi Michael, Yeah, if someone is writing to a file in a Samba share, and another user opens it up, they'll be notified that the file is currently in use, and that it's available for read only. This happens all of the time where I work (unfortunately). Depending on what kind of information is stored in your file, you may want to look into storing your data in a database. Hope this helps! --- Matt -----Original Message----- From: samba-bounces+mlozier=spindletopoil.com@lists.samba.org [mailto:samba-bounces+mlozier=spindletopoil.com@lists.samba.org] On Behalf Of Michael Dykstra Sent: Wednesday, December 19, 2007 10:20 PM To: samba@lists.samba.org Subject: [Samba] Unanswered question How long does one have to typically wait for an answer to a post? Tomorrow my message will have been up a week, and I've gotten no replies. It was about whether a file, while it was being written to, could subsequently be opened by another client for reading. I used a DVR with chasing play as an example. Didn't seem like that difficult of a question, but maybe it isn't geeky enough for some. (Or perhaps the answer is "No" and people are too embarrassed to admit Samba can't do it.) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba