On 18 August 2013, Guy Ferguson wrote:
[...]
> BUt I am trying to handle the chroot issue by using a hack I found online:
>
> ### in /etc/rc.local:
> # mysql server
> if [ -x /usr/local/bin/mysqld_safe ] ; then
> su -c mysql root -c '/usr/local/bin/mysqld_safe >/dev/null
Cheers.
I'm testing that it's up and running - "fstat | grep "*:" | grep mysql
...which outputs (from memory) a line indicating it works - something like:
internet stream tcp .*:3306
So it's running.
BUt I am trying to handle the chroot issue by using a hack I found online:
Need more info, like exactly how you're checking whether mysql works or
not. But from your message you're apparently running into chroot issues:
http://www.openbsd.org/faq/faq10.html#httpdchroot
On Sat, Aug 17, 2013 at 8:52 PM, Guy Ferguson wrote:
> Hello,
>
> First time user of OpenBSD here.
Hello,
First time user of OpenBSD here. Having issues getting mysql up and running
Can I ask you to confirm that in OpenBSD 5.3 mysql.sock should be being
created in/var/run/mysql or in/var/mysql?
This page
(http://www.openbsd.org/cgi-bin/cvsweb/ports/databases/mysql/Makefile?rev=1.21
> Here's an addition of opening quotes in this INSTALL file:
Fixed. Thanks!
Miod
On Sat, Aug 17, 2013 at 10:51:36PM +0100, Mik J wrote:
> Hello,
>
> In my message log file I have
> /bsd: wd1g: uncorrectable data error
> reading fsbn 27690576 of 27690560-27690591 (wd1 bn 1951859792; cn 121497 tn
> 166 sn 29), retrying
>
> I used the badblocks utility an checked the whole disk
2013/8/17 Mik J :
> I used the badblocks utility an checked the whole disk
> and only this block number is faulty.
What do the smartmontools tell you?
> Since I believe my disk is ok
It is not. Do you have backups?
Best
Martin
I haven't seen this mentioned in current.html, so..
If you're using mutt's caching options (set header_cache,
set message_cachedir), clear the cache before upgrading
to newer snapshot if you're not a fan of 1.4G core files
lying around.
Hello,
In my message log file I have
/bsd: wd1g: uncorrectable data error
reading fsbn 27690576 of 27690560-27690591 (wd1 bn 1951859792; cn 121497 tn
166 sn 29), retrying
I used the badblocks utility an checked the whole disk
and only this block number is faulty.
I tried to override it with zeros
Hello misc@
I did a few quick google searches, and I can't turn up the status of messa
9.1+ on OpenBSD
there are a few commit references in xenocara, that would lead one to
believe mesa 9+ is
being worked on.
I would like to run mesa 9.1+ with readon-kms, and im looking for a work in
progress por
Sorry for the noise. Should have read the FAQ first...
http://www.openbsd.org/faq/current.html#20130812 explains the required
firmware.
It's working now.
On Sat, Aug 17, 2013, at 10:48, Byron Klippert wrote:
> On Sat, Aug 17, 2013, at 2:07, Jonathan Gray wrote:
> > Did you install the firmware
On Sat, Aug 17, 2013, at 2:07, Jonathan Gray wrote:
> Did you install the firmware first?
Firmware?
> It seems odd that wsdisplay is not listed in your dmesg, is
> that just an omission on your side?
The dmesg below is what was stored to /var/run/dmesg.boot which I was
able to copy once booted
On Sat, Aug 17, 2013 at 01:03:28PM +0100, James Griffin wrote:
> Hi
>
> Today I used the Aug 12 snapshot files to upgrade. It wasn't successful
> as I did not read the notes at [1]. I had become complacent WRT upgrades
> as over the last 6 months they've been extremely straight forward and I
> fo
Hi
Today I used the Aug 12 snapshot files to upgrade. It wasn't successful
as I did not read the notes at [1]. I had become complacent WRT upgrades
as over the last 6 months they've been extremely straight forward and I
foolishly assumed this one would be too.
Anyway, after finding myself locked
Here's an addition of opening quotes in this INSTALL file:
--- INSTALL.i386.53 Wed Mar 13 00:58:19 2013
+++ INSTALL.i386.changedSat Aug 17 10:11:40 2013
@@ -359,7 +359,7 @@
upgrading. (If you are upgrading, it's recommended that
you get a copy of this
Did you install the firmware first?
It seems odd that wsdisplay is not listed in your dmesg, is
that just an omission on your side?
Anyway to get some more information you could build a kernel with:
Index: drmP.h
===
RCS file: /cvs/
On Fri, Aug 16, 2013 at 08:34:51PM +0100, Craig R. Skinner wrote:
> The existing grammar is erratic:
>
> $ fgrep filesystem dump.8 | wc -l
> 15
> $ fgrep 'file system' dump.8 | wc -l
> 6
>
erratic, you say?
$ grep -i "filesystem" restore.8 | wc -l
0
$ grep -i
Hello misc,
Thought I'd share my recent snapshot experience...
Can't boot the latest snapshot (Aug-14) on my machine, I assume it has
something to do with the latest radeondrm changes
(http://undeadly.org/cgi?action=article&sid=20130812135734&mode=expanded&count=7).
I'm attempting to boot from
18 matches
Mail list logo