print/cups: PageLog remains empty

2015-08-22 Thread Dr. Peter Voigt
I have reinstalled my server with 10.2-RELEASE (amd64). I have detected that my PageLog file of cups remains empty while my AccessLog and ErrorLog files are filled as expected. Otherwise printing is working fine. When comparing my cups configuration with my various Linux machines there appears no

Re: Removal of print/ghostscript*-nox11

2015-08-22 Thread Hiroki Sato
Hiroki Sato wrote in <20150821.022521.792759762853683209@allbsd.org>: hr> So I would suggest either of the following two plans: hr> hr> Plan A: Just remove print/ghostscript*-nox11. ... hr> Plan B: Remove print/ghostscript*-nox11 and split the X11-dependent hr> part of print/gh

Re: Removal of print/ghostscript*-nox11

2015-08-22 Thread Warren Block
On Sun, 23 Aug 2015, Hiroki Sato wrote: Hiroki Sato wrote in <20150821.022521.792759762853683209@allbsd.org>: hr> So I would suggest either of the following two plans: hr> hr> Plan A: Just remove print/ghostscript*-nox11. ... hr> Plan B: Remove print/ghostscript*-nox11 and split the X

Re: Removal of print/ghostscript*-nox11

2015-08-22 Thread Hiroki Sato
Warren Block wrote in : wb> It's not clear to me how people that currently have the old wb> print/ghostscript should switch to the new version. wb> wb> 'portmaster -o print/ghostscript9-x11 ghostscript9-9.06_10' (in my wb> case) or even just 'portmaster ghostscript9-9.06_10' turns into an wb> e

FreeBSD Port: sshguard-ipfw-1.6.1 Problem

2015-08-22 Thread khansen
I've been having a problem with sshguard-ipfw on the following armv6 platforms: RPI-B RPI2 BeagleBone Black Since upgrading sshguard-ipfw from 1.5.X to 1.6.X (including the latest 1.6.1 from the ports tree), sshguard builds and runs but crashes with a dump as soon as a condition is reached where

Re: Removal of print/ghostscript*-nox11

2015-08-22 Thread Stari Karp
On Sat, 2015-08-22 at 14:55 -0600, Warren Block wrote: > On Sun, 23 Aug 2015, Hiroki Sato wrote: > > > Hiroki Sato wrote > > in <20150821.022521.792759762853683209@allbsd.org>: > > > > hr> So I would suggest either of the following two plans: > > hr> > > hr> Plan A: Just remove print/ghos

Re: Removal of print/ghostscript*-nox11

2015-08-22 Thread Warren Block
On Sun, 23 Aug 2015, Hiroki Sato wrote: Warren Block wrote in : wb> It's not clear to me how people that currently have the old wb> print/ghostscript should switch to the new version. wb> wb> 'portmaster -o print/ghostscript9-x11 ghostscript9-9.06_10' (in my wb> case) or even just 'portmaster

Re: print/cups: PageLog remains empty

2015-08-22 Thread Kevin Oberman
On Fri, Aug 21, 2015 at 10:59 PM, Dr. Peter Voigt wrote: > I have reinstalled my server with 10.2-RELEASE (amd64). > > I have detected that my PageLog file of cups remains empty while my > AccessLog and ErrorLog files are filled as expected. Otherwise printing > is working fine. > > When comparin