On Mon, Jul 06, 2015 at 03:51:04PM +, Christian Weisgerber wrote:
>
> FWIW, this scheme is specified here:
>
> TR-187: IPv6 for PPP Broadband Access
> https://www.broadband-forum.org/technical/download/TR-187.pdf
>
Thanks for the information! There is no PPP involved in our situation
but ot
> Looks like there is no resolution but replacement. Thanks.
Yes, some overly generalised statements follow. A worthy endeavour
is to educate your users or use tools that prevent the problem.
Unless the entire software stack from the lowest level is encoding
aware and understands and carries corr
On 7/6/15, luke...@onemodel.org wrote:
> I'm on OpenBSD 5.7 amd64, w/ all the latest stable patches. When I simply
> launch xfce (from ports), an xterm, and ~34 "xedit" windows, I get:
> "Maximum number of clients reachedError: Can't open display: :0.0". I
> think I also had the same problem earl
On 07/06/15 22:43, luke...@onemodel.org wrote:
I'm on OpenBSD 5.7 amd64, w/ all the latest stable patches. When I simply
launch xfce (from ports), an xterm, and ~34 "xedit" windows, I get:
"Maximum number of clients reachedError: Can't open display: :0.0". I
think I also had the same problem ear
I'm on OpenBSD 5.7 amd64, w/ all the latest stable patches. When I simply
launch xfce (from ports), an xterm, and ~34 "xedit" windows, I get:
"Maximum number of clients reachedError: Can't open display: :0.0". I
think I also had the same problem earlier when running fvwm instead
of xfce.
I've sea
I'm on OpenBSD 5.7 amd64, w/ all the latest stable patches. When I simply
launch xfce (from ports), an xterm, and ~34 "xedit" windows, I get:
"Maximum number of clients reachedError: Can't open display: :0.0". I
think I also had the same problem earlier when running fvwm instead
of xfce.
I've sea
- Original Message -
| Looks like there is no resolution but replacement. Thanks.
|
| http://superuser.com/questions/302407/what-to-do-with-nfs-server-utf-8-and-wi
| ndows-7
|
| Best regards,
| Zhi-Qiang Lei
|
| > On Jul 6, 2015, at 1:56 PM, Johan Petersson wrote:
| >
| > i really wish
On Mon, 06 Jul 2015 16:53:27 +0200, Walter Alejandro Iglesias wrote:
> Till you mentioned about it I've ignored the existence of
> /usr/libexec/mail.local. :-) I'm a new to OpenBSD. Is it some kind of
> procmail's alike functionality?
It's what delivers messages to /var/mail/username when invok
On 2015-06-30, Patrik Lundin wrote:
> The setup looks like this: We are supposed to get a default route on the
> outside interface (em0), using autoconf, and then recieve an IPv6 prefix
> on the inside (em1) using DHCP6-PD (prefix delegation).
FWIW, this scheme is specified here:
TR-187: IPv6 f
It looks like this is fallout from the strtonum() conversion in
comsat. The issue is that mail.local writes a trailing newline
after the offset that we need to trim. This fixes it.
- todd
Index: libexec/comsat/comsat.c
===
RCS fil
Hello Todd,
On Mon, Jul 06, 2015 at 06:37:24AM -0600, Todd C. Miller wrote:
> Is your mail being delivered to /var/mail/yourname or do you have
> a .forward file? The comsat daemon is notified by mail.local which
> delivers mail to the local mail spool. If you have a .forward file,
> mail.local
Is your mail being delivered to /var/mail/yourname or do you have
a .forward file? The comsat daemon is notified by mail.local which
delivers mail to the local mail spool. If you have a .forward file,
mail.local is not used and you won't get a biff notification.
- todd
12 matches
Mail list logo
