I ran into this exact same issue when I was trying to create a
rollback install with CRYPTO for a sort of appliance I develop/manage
for my company. We only have remote access with console and remote
hands aren't easy to get so when upgrading it'd be nice to have a
rollback in case something happen
inteldrm seems to block USB output during scrolling.
sox and other programs sending directly to the audio
device work perfectly unless the inteldrm console
changes. Then multiple short dropouts occur sounding
like scratches.
I don't see any errors logged anywhere.
Has anyone seen this?
Geoff S
On 2015-11-08 13.28.32 -0700, bluesun08 wrote:
> Back to the problem: I think OpenBSD need a patch for PostgreSQL
To get it into ports, send your patch to po...@openbsd.org and CC the
database/postgresql maintainer (Pierre-Emmanuel Andre ).
Please upstream your patch, too. There's an extensive FA
$cat sndiod-log
snd0 pst=cfg.default: rec=0:1 play=0:1 vol=23170 dup
listen(/tmp/aucat/aucat0|ini): created
this is very strange, sndiod would have logged all the audio
traffic. Could you check that this is the right file or that
programs are not bypassing sndiod for any reason ?
It's the ri
Em 08-11-2015 20:14, Jeremy escreveu:
> I suspect the change in PID is as a result of the previous instance
> having been killed and the error message coming from the new instance
> being (re)started with an invalid argument.
>
>
> Looks like the problem is with Webmin. I've updated its config to
> Hi,
>
> I'm trying to relay a broadcast message.
>
> I've tried the following in pf :
>
> pass in quick proto udp from any to vlan1:broadcast port 3121 rdr-to
> vlan3:broadcast port 3121
> pass out quick on vlan3 from any to vlan3:broadcast nat-to vlan3
>
> with no success any chance to do it wit
I suspect the change in PID is as a result of the previous instance
having been killed and the error message coming from the new instance
being (re)started with an invalid argument.
Looks like the problem is with Webmin. I've updated its config to
use /etc/rc.d/dhcpd start/stop/restart instead of
On Sun, Nov 8, 2015 at 3:35 PM, Jeremy wrote:
> No I only have one instance running.
>
> # ps aux | grep dhcp
> _dhcp 7784 0.0 0.1 756 1340 ?? Ss 9:00AM0:00.00
> /usr/sbin/dhcpd em0
Interesting a bit that the log shows two different PID's - it changes
between 08:25:34 and 08:25
I beg your pardon - i was cynical!
Back to the problem: I think OpenBSD need a patch for PostgreSQL that uses
ICU, like this one for FreeBSD (because i don't know how to do it manually):
http://people.freebsd.org/~girgen/postgresql-icu/README.html
--
View this message in context:
http://ope
No I only have one instance running.
# ps aux | grep dhcp
_dhcp 7784 0.0 0.1 756 1340 ?? Ss 9:00AM0:00.00
/usr/sbin/dhcpd em0
root 19515 0.0 0.0 164 328 p0 R+ 9:14AM0:00.00 grep dhcp
I'm concerned at the "Can't open f:" message which I'm guessing is
looking
Don't insult other people on the mailing list.
--
SCCS, the source motel! Programs check in and never check out!
-- Ken Thompson
On Sun, Nov 08, 2015 at 06:57:23PM +0100, Gregor Best wrote:
> [...]
> If it helps debugging this, I can give SSH access to the router,
> provided that reboots don't happen between 18:00 and 02:00 German time
> too often, since that's when we have larger amounts of visitors in our
> hackerspace.
>
On Mon, Nov 02, 2015 at 09:29:20PM +0100, Gregor Best wrote:
> [...]
> Looks good so far. I've run a few light tests and the usual load that
> caused the timeouts before, haven't seen any yet.
> [...]
I just checked back on the router and it seems that the patch doesn't
help after all :( The numbe
On 2015-11-08, bluesun08 wrote:
> "OpenBSD doesn't provide LC_COLLATE locales. " ?
>
> We are in 2015 and i thought OpenBSD is a up-to-date server operating
> system.
> So OpenBSD is not recommended for practical use or a postgresql database
> server.
I don't know how you go from "doesn't su
On Sun, Nov 08, 2015 at 06:29:22AM -0700, bluesun08 wrote:
> "OpenBSD doesn't provide LC_COLLATE locales. " ?
>
> We are in 2015 and i thought OpenBSD is a up-to-date server operating
> system.
> So OpenBSD is not recommended for practical use or a postgresql database
> server.
> No wonder th
> So OpenBSD is not recommended for practical use or a postgresql database
> server.
> No wonder that most professional users switch to linux.
>
> No harm meant!
You are retard, go away and don't return then.
j.
"OpenBSD doesn't provide LC_COLLATE locales. " ?
We are in 2015 and i thought OpenBSD is a up-to-date server operating
system.
So OpenBSD is not recommended for practical use or a postgresql database
server.
No wonder that most professional users switch to linux.
No harm meant!
--
View th
On 2015-11-08, bluesun08 wrote:
> But when i type "locale -a" i get:
> ...
> de_AT.ISO8859-1
> de_AT.ISO8859-15
> de_AT.UTF-8
> de_CH.ISO8859-1
> de_CH.ISO8859-15
> de_CH.UTF-8
> de_DE.ISO8859-1
> de_DE.ISO8859-15
> de_DE.UTF-8
> el_GR.ISO8859-7
> el_GR.UTF-8
> ...
>
> So the locale "de_DE.UTF-8"
On Sun, 8 Nov 2015 11:52:48 +0100
Stefan Sperling wrote:
> On Sat, Nov 07, 2015 at 07:57:05PM -0500, Jonathan Thornburg wrote:
>> At this point the machine can boot and run sd1[aeg] fine. *But* if I
>> enter "boot sr1d:/bsd" at the "boot>" prompt, the machine boots sd1[aeg],
>> not the desired sd
On Sun, Nov 08, 2015 at 04:03:05AM -0700, bluesun08 wrote:
> But when i type "locale -a" i get:
> ...
> de_AT.ISO8859-1
> de_AT.ISO8859-15
> de_AT.UTF-8
> de_CH.ISO8859-1
> de_CH.ISO8859-15
> de_CH.UTF-8
> de_DE.ISO8859-1
> de_DE.ISO8859-15
> de_DE.UTF-8
> el_GR.ISO8859-7
> el_GR.UTF-8
> ...
>
>
But when i type "locale -a" i get:
...
de_AT.ISO8859-1
de_AT.ISO8859-15
de_AT.UTF-8
de_CH.ISO8859-1
de_CH.ISO8859-15
de_CH.UTF-8
de_DE.ISO8859-1
de_DE.ISO8859-15
de_DE.UTF-8
el_GR.ISO8859-7
el_GR.UTF-8
...
So the locale "de_DE.UTF-8" exist. What goes wrong?
--
View this message in context:
ht
On Sat, Nov 07, 2015 at 07:57:05PM -0500, Jonathan Thornburg wrote:
> At this point the machine can boot and run sd1[aeg] fine. *But* if I
> enter "boot sr1d:/bsd" at the "boot>" prompt, the machine boots sd1[aeg],
> not the desired sd1[dfh]. In other words, at this point my "backup"
> sd1[dfh] p
> On 08/11/15 04:26, Eric Furman wrote:
> I'm not a troll. Just saw the thread on Slashdot and thought it
> would be interesting to see what other people thought.
>
> I'll refrain from posting such things in the future if the only
> response I get is being called a troll (which is a really
> unimag
23 matches
Mail list logo
