[imp] Bad escape sequence

[Mark Orenstein]

I think with your comments, Ive found it. Yesterday, I searched for .rpmorig
and didn't find anything.  Today, after looking in horde-phplib for
local.inc, I found

-rw-r-----    1 root     nobody       3281 Oct 31 14:58 local.inc
-rw-r-----    1 root     nobody       3283 Oct 31 14:45 local.inc.bak
-rw-r-----    1 root     nobody       3217 Oct  3 14:08 local.inc.rpmsave

Note the .rpmsave (versue .rpmorig).  var $Password has the updated password
in both local.inc and local.inc.rpmsave.  var $Password has value 'hordemgr'
in local.inc.bak.

If defaults.php3 is written from the "browser screen", then it had the
updated password.  When I executed dbpasswd.sh yesterday, I had to enter the
updated password three time, once to get into the script and twice to change
it to the updated password.  So probably the only place I messed up was in
not restoring local.inc.rpmsave.

By the way, one more question or request for enhancement.  Is there any way
through imp for an email only user to change his password?  I didn't see
any.

Mark Orenstein


-----Original Message-----
From: Brent J. Nordquist [mailto:bjn@horde.org]
Sent: Wednesday, November 01, 2000 10:05 AM
To: imp@lists.horde.org
Subject: RE: [imp] Bad escape sequence


On Tue, 31 Oct 2000, Mark Orenstein <morenstein@alum.mit.edu> wrote:

> I installed the RH6.2 Oct. security advisories include Apache 1.3.14
> and PHP 3.0.17-1.6.2horde1.  I then did the RPM upgrade install to
> horde 1.2.3-1 and imp 2.2.3-1 and the "bad escape sequence" message
> when adding an entry to the address book no longer appears.

Good deal.

> I did still run into one problem doing the upgrade.  I had changed the
> hordemgr password as part of the original install and imp 2.2.3 would
> not come up until I reran horde/scripts/database/dbpasswd.sh using the
> same (old) password.  I'm using MySQL.

Interesting!  Did you look for any .rpmorig files left behind after you
upgraded (I assume by that you mean "rpm -U") -- it's possible that
horde/phplib/local.inc with your password was shoved aside in favor of the
default one.  (We don't do the ".dist" thing with that one as we do with
the others.)

Can you be more specific about "would not come up" -- what symptom did you
see?  I'm curious which of the three places (MySQL itself, local.inc, or
defaults.php3) had the wrong password.

--
Brent J. Nordquist <bjn@horde.org>
Yahoo!: Brent_Nordquist / AIM: BrentJNordquist / ICQ: 76158942


--
IMP mailing list: http://horde.org/imp/
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: imp-unsubscribe@lists.horde.org