Re: f86OpenWScons: cannot open /dev/ttyC4 (Permission denied)

2018-11-12 Thread d . rauschenb 
Hi,

do you run -current and you have upgraded just before this issue
occurs, than read current.html and switch to xenodm. Xorg is not
installed setiud anymore. This means you cannot run startx anymore as
user.

-dra

On Mon, Nov 12, 2018 at 02:21:36PM +0100, Krzysztof Strzeszewski wrote:
> Hi,
> 
> why I can't run Xorg?
> 
> My 10-radeon.conf:
> 
> --
> #Section "OutputClass"
> 
> # Identifier "Radeon"
> # MatchDriver "radeon"
> # Driver "radeon"
> #EndSection
> 
> Section "Device"
>   Identifier "intel device"
>   Driver "intel"
> EndSection
> 
> --
> 
> I changed 10-radeon.conf, because when I have radeon, my log is writeing "no
> driver"
> 
> 
> __
> Regards,
> Krzysztof Strzeszewski
> 
> 
> 
> [ 186.207] X.Org X Server 1.19.6
> Release Date: 2017-12-20
> [ 186.207] X Protocol Version 11, Revision 0
> [ 186.207] Build Operating System: OpenBSD 6.4 amd64 [ 186.207] Current
> Operating System: OpenBSD krzych 6.4 GENERIC.MP#436 amd64
> [ 186.208] Build Date: 12 November 2018 12:20:38AM
> [ 186.208] [ 186.208] Current version of pixman: 0.34.0
> [ 186.208] Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> [ 186.208] Markers: (--) probed, (**) from config file, (==) default
> setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [ 186.209] (==) Log file: "/home/krzych/.local/share/xorg/Xorg.0.log", Time:
> Mon Nov 12 10:25:40 2018
> [ 186.210] (==) Using system config directory
> "/usr/X11R6/share/X11/xorg.conf.d"
> [ 186.210] (==) No Layout section. Using the first Screen section.
> [ 186.210] (==) No screen section available. Using defaults.
> [ 186.210] (**) |-->Screen "Default Screen Section" (0)
> [ 186.210] (**) | |-->Monitor ""
> [ 186.210] (==) No device specified for screen "Default Screen Section".
> Using the first device section listed.
> [ 186.210] (**) | |-->Device "intel device"
> [ 186.210] (==) No monitor specified for screen "Default Screen Section".
> Using a default monitor configuration.
> [ 186.210] (==) Automatically adding devices
> [ 186.210] (==) Automatically enabling devices
> [ 186.210] (==) Not automatically adding GPU devices
> [ 186.211] (==) Max clients allowed: 256, resource mask: 0x1f
> [ 186.211] (==) FontPath set to:
> /usr/X11R6/lib/X11/fonts/misc/,
> /usr/X11R6/lib/X11/fonts/TTF/,
> /usr/X11R6/lib/X11/fonts/OTF/,
> /usr/X11R6/lib/X11/fonts/Type1/,
> /usr/X11R6/lib/X11/fonts/100dpi/,
> /usr/X11R6/lib/X11/fonts/75dpi/
> [ 186.211] (==) ModulePath set to "/usr/X11R6/lib/modules"
> [ 186.211] (II) The server relies on wscons to provide the list of input
> devices.
> If no devices become available, reconfigure wscons or disable
> AutoAddDevices.
> [ 186.211] (II) Loader magic: 0xf9721235000
> [ 186.211] (II) Module ABI versions:
> [ 186.211] X.Org ANSI C Emulation: 0.4
> [ 186.211] X.Org Video Driver: 23.0
> [ 186.211] X.Org XInput driver : 24.1
> [ 186.211] X.Org Server Extension : 10.0
> [ 186.211] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
> (Permission denied)
> Check that you have set 'machdep.allowaperture=1'
> in /etc/sysctl.conf and reboot your machine
> refer to xf86(4) for details
> [ 186.211] linear framebuffer access unavailable
> [ 186.211] (II) LoadModule: "glx"
> [ 186.214] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
> [ 186.219] (II) Module glx: vendor="X.Org Foundation"
> [ 186.219] compiled for 1.19.6, module version = 1.0.0
> [ 186.219] ABI class: X.Org Server Extension, version 10.0
> [ 186.220] (II) LoadModule: "intel"
> [ 186.221] (II) Loading /usr/X11R6/lib/modules/drivers/intel_drv.so
> [ 186.321] (II) Module intel: vendor="X.Org Foundation"
> [ 186.321] compiled for 1.19.6, module version = 2.99.916
> [ 186.321] Module class: X.Org Video Driver
> [ 186.321] ABI class: X.Org Video Driver, version 23.0
> [ 186.322] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
> i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
> 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
> Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
> GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
> [ 186.322] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
> [ 186.322] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
> [ 186.322] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200,
> 6200, P6300
> [ 186.323] (EE) Fatal server error:
> [ 186.323] (EE) xf86OpenWScons: cannot open /dev/ttyC4 (Permission
> denied)(EE) [ 186.323] (EE) Please consult the The X.Org Foundation support
> at http://wiki.x.org
> for help. [ 186.323] (EE) Please also check the log file at
> "/home/krzych/.local/share/xorg/Xorg.0.log" for additional information.
> [ 186.324] (EE) [ 186.333] (EE) Server terminated with error (1). Closing
> log file.

Re: Issue with OpenSMTPD, procmail and comsat

2018-09-03 Thread d . rauschenb 
Hi Gilles,

the following diff turns off the noise in /var/log/{messages,daemon}
but this is a hack and not a solution.

-dra

Index: comsat.c
===
RCS file: /cvs/src/libexec/comsat/comsat.c,v
retrieving revision 1.48
diff -u -p -r1.48 comsat.c
--- comsat.c3 Apr 2017 17:23:39 -   1.48
+++ comsat.c3 Sep 2018 15:23:23 -
@@ -221,7 +221,6 @@ mailfor(char *name)
cp[strcspn(cp, " \t\n")] = '\0';
offset = strtonum(cp, 0, LLONG_MAX, );
if (errstr) {
-   syslog(LOG_ERR, "'%s' is %s", cp + 1, errstr);
return;
}
while (--utp >= utmp) {

Re: Issue with OpenSMTPD, procmail and comsat

2018-09-03 Thread d . rauschenb 
Hi Gilles,

On Mon, Sep 03, 2018 at 02:27:26PM +0200, Gilles Chehade wrote:
> On Mon, Sep 03, 2018 at 12:25:55PM +0200, d.rausch...@gmail.com wrote:
> > On Sun, Sep 02, 2018 at 01:25:46PM +0200, Gilles Chehade wrote:
> > 
> > From d...@ws.lan  Mon Sep  3 12:12:34 2018
> > 
> can you try:
> 
> procmail -f %{mbox.from} --

Not working. The two spaces betweem the mail address and the date do
not only occur in /var/mail/$USER they also appear in the filtered
mails.  Of course comsat(8) is not looking at them and my mail
user-agent (mutt) is accepting the two spaces.

-dra

Re: Issue with OpenSMTPD, procmail and comsat

2018-09-03 Thread d . rauschenb 
Hi Gilles,

On Sun, Sep 02, 2018 at 01:25:46PM +0200, Gilles Chehade wrote:
> Can you provide me with the corrupt line procmail includes so I can
> check if it is invalid indeed ?

The corrput line:

>From d...@ws.lan  Mon Sep  3 12:12:34 2018

The differenc I encountered is with .forward to procmail there are
TWO spaces between the email address and the date, without .forward to
procmail there is only ONE space.

If I edit such a two spaced mail with vi(1) and concat it to
/var/mail/$USER comsat(8) is silenced. No error message but ksh
reports "you have mail in /var/mail/dra" as it should.

-dra

Issue with OpenSMTPD, procmail and comsat

2018-09-02 Thread d . rauschenb 
Hi,

I figured out an issue with opensmtpd, procmail, and comsat.
The .forward for procamil must be

"|exec /usr/local/bin/procmail -f - || exit 75"

The -f - option makes procmail to include a dummy mail-from header
line. But this line is corrupt. comsat(8) does not like this:

Sep  1 19:10:41 ws comsat[11416]: ':/var/mail/dra' is invalid

in /var/log/messages. But mutt can read this mail.

Without the -f - option in the .forward file my mailspool is corrupted
because of the missin first line (mail-from header). The currect
solution is: I have turned off comsat in inetd.conf. But i am
unsatisfied with this. It would be better if opensmtpd would include
the mail-from header if processinf the .forward to procmail.

-dra