Re: DBaccessError when switching which user 'runs' the spyce server
"Jason Persampieri" <[email protected]> Wed, 9 Jan 2008 11:23:01 -0500
| Newsgroups | gmane.comp.python.spyce.general |
|---|---|
| Message-ID | <[email protected]> |
--===============1976385856== Content-Type: multipart/alternative; boundary="----=_Part_8488_27014817.1199895781757" ------=_Part_8488_27014817.1199895781757 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Jan 9, 2008 1:19 AM, Jonathan Ellis <[email protected]> wrote: > On Wed, 9 Jan 2008 00:14:54 -0500, "Jason Persampieri" > <[email protected]> said: > > It turns out that the spyce server was using the same 'spysession' temp > > file > > for the two runs. And seeing as how it was initially created as 'root', > > the > > measly 'apache' user couldn't access it. Is this by design? It seems > > like > > the server should start a new session file every time it's run, yes? > > Since the whole point of sessions is to make a stateless protocol more > stateful, that doesn't necessarily follow at all in my mind. :) > > Think of it this way: if you were sharing a session db across N servers > (spyce doesn't have a db backend yet, but hypothetically :) you wouldn't > want to reset it if one server crashed and restarted for any N > 1. So > really it would be confusing to blow it away if N = 1. > > (Yes, this is how all the other session systems I know of work too, it's > not just a Spyce quirk.) > > -Jonathan > Um... yes... well.... that makes entirely too much sense :) If I had known more about 'shelve' and the idea of a stateful server, I would have found the error much faster. Ah well. Perhaps there could simply be a more informative error message? _jason ------=_Part_8488_27014817.1199895781757 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Jan 9, 2008 1:19 AM, Jonathan Ellis <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Wed, 9 Jan 2008 00:14:54 -0500, "Jason Persampieri"<br><<a href="mailto:[email protected]">[email protected]</a>> said:<br>> It turns out that the spyce server was using the same 'spysession' temp <br>> file<br>> for the two runs. And seeing as how it was initially created as 'root',<br>> the<br>> measly 'apache' user couldn't access it. Is this by design? It seems<br>> like<br> > the server should start a new session file every time it's run, yes?<br><br></div>Since the whole point of sessions is to make a stateless protocol more<br>stateful, that doesn't necessarily follow at all in my mind. :) <br><br>Think of it this way: if you were sharing a session db across N servers<br>(spyce doesn't have a db backend yet, but hypothetically :) you wouldn't<br>want to reset it if one server crashed and restarted for any N > 1. So <br>really it would be confusing to blow it away if N = 1.<br><br>(Yes, this is how all the other session systems I know of work too, it's<br>not just a Spyce quirk.)<br><font color="#888888"><br>-Jonathan<br></font></blockquote> </div><br>Um... yes... well.... that makes entirely too much sense :)<br><br>If I had known more about 'shelve' and the idea of a stateful server, I would have found the error much faster. Ah well.<br><br>Perhaps there could simply be a more informative error message? <br><br>_jason<br> ------=_Part_8488_27014817.1199895781757-- --===============1976385856== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace --===============1976385856== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Spyce-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/spyce-users --===============1976385856==--