At 01:41 PM 6/25/2004, Ken Jones wrote:
On Friday 25 June 2004 02:40 pm, Paul Theodoropoulos wrote:
> At 12:33 PM 6/25/2004, Ken Jones wrote:
> >What you can do is keep the original data, then update and add a domain.
> >If it doesn't work, put the old data back. It only is used when adding
> > dom
On Friday 25 June 2004 03:41 pm, Ken Jones wrote:
> On Friday 25 June 2004 02:40 pm, Paul Theodoropoulos wrote:
> > At 12:33 PM 6/25/2004, Ken Jones wrote:
> > >What you can do is keep the original data, then update and add a domain.
> > >If it doesn't work, put the old data back. It only is used w
On Friday 25 June 2004 02:40 pm, Paul Theodoropoulos wrote:
> At 12:33 PM 6/25/2004, Ken Jones wrote:
> >What you can do is keep the original data, then update and add a domain.
> >If it doesn't work, put the old data back. It only is used when adding
> > domains not users.
>
> thanks. so my specul
At 12:33 PM 6/25/2004, Ken Jones wrote:
What you can do is keep the original data, then update and add a domain.
If it doesn't work, put the old data back. It only is used when adding domains
not users.
thanks. so my speculation that the 'dom_89' user is sort of a
'master' field for such things i
On Friday 25 June 2004 12:07 pm, Paul Theodoropoulos wrote:
> indeed, but i can't take that risk without knowing the specific details for
> sure. this is a production system with thousands of customers.
>
> would Bill Shupp possibly know?
I wrote the code. Bill might know.
What you can do is keep
indeed, but i can't take that risk without knowing the specific details for
sure. this is a production system with thousands of customers.
would Bill Shupp possibly know?
At 10:00 AM 6/25/2004, Ken Jones wrote:
It might be as simple as changing the two "5" entries to "0"
which from your listing b
It might be as simple as changing the two "5" entries to "0"
which from your listing below looks like the level_index0 and the_dir columns
Ken Jones
On Friday 25 June 2004 11:23 am, Paul Theodoropoulos wrote:
> sooo - nobody knows where the directory 'incrementer' lives? Tom? i have no
> fix? i'm
On Jun 25, 2004, at 9:23 AM, Paul Theodoropoulos wrote:
sooo - nobody knows where the directory 'incrementer' lives? Tom? i
have no fix? i'm stuck with going from
/u1/domains/0/abc.com to
/u1/domains/5/def.com
?? no way to get the system to resume creating new domains under the
more logical /u
sooo - nobody knows where the directory 'incrementer' lives? Tom? i have no
fix? i'm stuck with going from
/u1/domains/0/abc.com to
/u1/domains/5/def.com
?? no way to get the system to resume creating new domains under the more
logical /u1/domains/1/def.com?
i mean, yeah - i can live with it.
> At 12:31 PM 6/23/2004, Jeremy Kitchen wrote:
[snip]
>>phpmyadmin (http://phpmyadmin.sf.net) makes working with mysql very easy
>> :)
>
> that it does, but it can also lower your effective security, by creating
> Yet Another Thing To Crack.
>
chmod -R ugo-rwx phpmyadmin/
safety first! ;-) I keep
On Wed, 2004-06-23 at 14:35, Paul Theodoropoulos wrote:
> At 12:31 PM 6/23/2004, Jeremy Kitchen wrote:
> >On Wednesday 23 June 2004 02:16 pm, Paul Theodoropoulos wrote:
> > > so, if anyone can confirm my speculations, and suggest how to fix it
> > > (that's right, i've never inserted data manually
At 12:31 PM 6/23/2004, Jeremy Kitchen wrote:
On Wednesday 23 June 2004 02:16 pm, Paul Theodoropoulos wrote:
> so, if anyone can confirm my speculations, and suggest how to fix it
> (that's right, i've never inserted data manually into a table!), i'd
> appreciate the help.
phpmyadmin (http://phpmyad
On Wednesday 23 June 2004 02:16 pm, Paul Theodoropoulos wrote:
> so, if anyone can confirm my speculations, and suggest how to fix it
> (that's right, i've never inserted data manually into a table!), i'd
> appreciate the help.
phpmyadmin (http://phpmyadmin.sf.net) makes working with mysql very ea
well, now it's incremented up to '5'. eesh. what i've found in perusing the
mysql backend db, is the following:
mysql> select * from dir_control where domain = 'dom_89';
++---+---+---+--+--+--+++--
14 matches
Mail list logo