One more step towards OT, and yet on the spot. Now it is on 'beauty'.
At shutdown, we get always
"stopping package daemons:/etc/rc[260]: /etc/rc.d/: cannot execute -
Is a directory"
Is there anything wrong, still, with our configuration?
Uwe
On 2012-03-14, Uwe Dippel wrote:
> I had read those. And yet, I don't understand that line. It doesn't
> look like it should be written into rc.conf / rc.conf.local, does it?
> Correct me if I'm wrong. It looks like a shell variable that has
> 'postfix' appended.
rc.conf / rc.conf.local *are* she
Hi Uwe,
On Wed Mar 14 2012 22:47, Uwe Dippel wrote:
> On Wed, Mar 14, 2012 at 10:22 PM, Uwe Dippel wrote:
>
> > I had read those. And yet, I don't understand that line. It doesn't
> > look like it should be written into rc.conf / rc.conf.local, does it?
> > Correct me if I'm wrong. It looks like
On Wed, Mar 14, 2012 at 10:22 PM, Uwe Dippel wrote:
> I had read those. And yet, I don't understand that line. It doesn't
> look like it should be written into rc.conf / rc.conf.local, does it?
> Correct me if I'm wrong. It looks like a shell variable that has
> 'postfix' appended.
Ooops, I thin
On Wed, Mar 14, 2012 at 8:35 PM, Rodolfo Gouveia wrote:
>> And slightly OT: I have stared at the
>> pkg_scripts="${pkg_scripts} postfix" in the Upgrade Guide, and still
>> don't grasp what this is supposed to do, and where; since I am running
>> postscript.
>
> http://www.openbsd.org/faq/faq10.ht
On Wed, Mar 14, 2012 at 08:21:43PM +0800, Uwe Dippel wrote:
> I don't get yet which utility starts and controls the package scripts in rc.d.
> And slightly OT: I have stared at the
> pkg_scripts="${pkg_scripts} postfix" in the Upgrade Guide, and still
> don't grasp what this is supposed to do, and
On Wed, Mar 14, 2012 at 6:55 PM, Fred Crowson wrote:
> What does your logs say in /var/mysql/ ?
>
> hth
Yes, Fred, very much! - It is obvious that I failed - and still fail -
to understand the new startup system. Can anyone point me to a
complete overview to read up on it?
I don't get yet which
check phpinfo() and determine whether the extension is not being
loaded, or whether it is loaded but the connection is failing.
On 2012-03-14, Uwe Dippel wrote:
> I have this unfortunate occurrence on one of my production machines:
> "Database Error: Unable to connect to the database:Could not c
On Wed, Mar 14, 2012 at 7:27 PM, Norman Golisz wrote:
> However, did you change any values in php.ini from default?
no, not yet. I wasn't actually expecting everything to be up 100%, but
to be up, with the 50-default php-5.2.ini. Or, with the previous
php.ini in that place.
I also looked at the
On Wed Mar 14 2012 11:59, Norman Golisz wrote:
> Hi Uwe,
>
> On Wed Mar 14 2012 17:53, Uwe Dippel wrote:
> > I have this unfortunate occurrence on one of my production machines:
> > "Database Error: Unable to connect to the database:Could not connect to
> > MySQL"
> > I studied the Upgrade Guide
Hi Uwe,
On Wed Mar 14 2012 17:53, Uwe Dippel wrote:
> I have this unfortunate occurrence on one of my production machines:
> "Database Error: Unable to connect to the database:Could not connect to MySQL"
> I studied the Upgrade Guide 4.9 to 5.0 intensely before and after, but
> can't find what wen
On 14 March 2012 09:53, Uwe Dippel wrote:
> I have this unfortunate occurrence on one of my production machines:
> "Database Error: Unable to connect to the database:Could not connect to
MySQL"
> I studied the Upgrade Guide 4.9 to 5.0 intensely before and after, but
> can't find what went wrong. I
I have this unfortunate occurrence on one of my production machines:
"Database Error: Unable to connect to the database:Could not connect to MySQL"
I studied the Upgrade Guide 4.9 to 5.0 intensely before and after, but
can't find what went wrong. I just did the upgrade, and made the links
as propos
13 matches
Mail list logo
