On Wed, Jul 10, 2013 at 12:01:11AM +0300, Tony Berth wrote:
> is anyone using goaccess 0.5 with 5.2 or 5.3?
>
> When running './configure' I get:
>
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir
On the FAQ of the project website, you will find a how-to compile it
on OpenBSD, you need to edit 2 or 3 files before compiling it.
2013/7/9 Tony Berth :
> is anyone using goaccess 0.5 with 5.2 or 5.3?
>
> When running './configure' I get:
>
> checking for a BSD-compatible install... /usr/bin/inst
On Wed, Jul 10, 2013 at 12:01:11AM +0300, Tony Berth wrote:
> is anyone using goaccess 0.5 with 5.2 or 5.3?
>
> When running './configure' I get:
>
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir
is anyone using goaccess 0.5 with 5.2 or 5.3?
When running './configure' I get:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
Hi Jan.
On Tue, 9 Jul 2013 10:22:48 +0200
Jan Stary wrote:
> > mount \\192.168.2.108\usr\src\media H:
>
> Details matter. Is this NFS2/NFS3? Is this a tcp/udp mount?
> mount_nfs (as we know it on BSD) offers quite a few options
> that can make a difference. Does the Win client have any
> option
On 2013-07-09, Jan Stary wrote:
> So the last thing in the kdump is the sucessfull call
> to the (eventually) found 'xterm'. Why is that?
This is probably because of the setgid bit. You could try "sudo ktrace -i
xterm"...
On Tue, Jul 09, 2013 at 09:37:06PM +0300, ?zg?r Kazan??? wrote:
> And the browser side:
> "502 Bad Gateway"
> (Actually the same error occurs when trying with any filenames (no matter
> exists or not) ended with .cgi.
... and the log probably says "upstream prematurely closed FastCGI
stdout". Wha
On Tue, Jul 09, 2013 at 09:18:40PM +0300, ?zg?r Kazan??? wrote:
> It's the base' perl,
>
> # perl -v
> This is perl 5, version 12, subversion 2 (v5.12.2 (*)) built for
> amd64-openbsd
> (with 10 registered patches, see perl -V for more detail)
>
> And using nginx with chroot-disabled, (-u) didn't
On 2013-07-09 13:18, Özgür Kazanççı wrote:
And using nginx with chroot-disabled, (-u) didn't help neither.
That isn't surprising, because nginx's chroot won't affect things run
by slowcgi (which chroots itself separately). Also, when running with
nginx chroot disabled, did you also adjust pat
On Jul 09 14:11:01, na...@mips.inka.de wrote:
> Jan Stary wrote:
>
> > > 1) running cwm(1) with having
> > > 2) ``XTerm*locale:ISO8859-1'' in ~/.Xresources
> > > 3) hitting CM-Return starts xterm(1) after differing amounts of retries
> > >(between 1 and 9 up to now).
> >
> > http://marc.inf
It's the base' perl,
# perl -v
This is perl 5, version 12, subversion 2 (v5.12.2 (*)) built for
amd64-openbsd
(with 10 registered patches, see perl -V for more detail)
And using nginx with chroot-disabled, (-u) didn't help neither.
"If you just want to see if nginx works try /var/www/cgi-bin/tes
On Tue, Jul 09, 2013 at 08:30:03PM +0300, BSD Kazakhstan wrote:
> Thinking of chroot(), I have even tried adding a copy of perl binary to:
>
> # ls -l /var/www/usr/bin/
> -rwxr-xr-x 1 root daemon 10725 Jul 9 19:15 perl
your perl is probably not statically linked, see
http://www.openbsd.org/fa
Hello everyone.
I'm having troubles of setting cgi/perl support for Nginx, on OpenBSD 5.3.
I get "502 Bad Gateway" on the browser when I type /cgi-bin/test.cgi -
which is a simple "Hello World" cgi file, doesn't work with my setup.
The error.log says:
[error] 29912#0: *6 upstream prematurely clo
Jan Stary wrote:
> > 1) running cwm(1) with having
> > 2) ``XTerm*locale:ISO8859-1'' in ~/.Xresources
> > 3) hitting CM-Return starts xterm(1) after differing amounts of retries
> >(between 1 and 9 up to now).
>
> http://marc.info/?l=openbsd-misc&m=137287894132390&w=2
> This exact problem w
On Jul 09 13:31:30, mcmer-open...@tor.at wrote:
> hello folks,
>
> when
> 1) running cwm(1) with having
> 2) ``XTerm*locale:ISO8859-1'' in ~/.Xresources
> 3) hitting CM-Return starts xterm(1) after differing amounts of retries
>(between 1 and 9 up to now).
>
> If I disable ``XTerm*locale:ISO
hello folks,
when
1) running cwm(1) with having
2) ``XTerm*locale:ISO8859-1'' in ~/.Xresources
3) hitting CM-Return starts xterm(1) after differing amounts of retries
(between 1 and 9 up to now).
If I disable ``XTerm*locale:ISO8859-1'' in ~/.Xresources the symptoms
are gone.
Bye, Marcus
Op
On Tue, Jun 26, 2012 at 09:46:23PM -0700, patrick keshishian wrote:
> [...]
> sleep-wake cycle test?
>
I had the problem again, and indeed, suspending the machine with zzz and
resuming it fixes audio input. Is there anything I can do to investigate
this? Dump some hardware registers before and af
* Riccardo Mottola [2013-07-08 17:09]:
> One of the drawback with this kernel is that I get a delay during boot:
>
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> <--- Several seconds delay --->
> mtrr: Pentium Pro MTRR support
> vscsi0
On Jul 08 22:07:53, pha...@gmx.de wrote:
> Hi David, hi Jan. Thanks for your response.
>
> On Mon, 8 Jul 2013 09:00:52 +0200
> Jan Stary wrote:
>
> > How is the filesystem mounted on the OpenBSD NFS server,
> > how is it exported, and how is it mounted on the Win client?
>
> the output of mount
19 matches
Mail list logo
