Re: [CentOS] Trouble setting up HP Officejet Pro 8600 printer on CentOS 7 + KDE

2016-11-11 Thread anax

Hi Niki
don't you need a hplip addon/plugin, which you can fetch from
http://hplipopensource.com/hplip-web/install/install/index.html

There, with the wizard, you get a file hplip-3.x.x.run
which you download and run using
bash hplip-3.x.x.run

This will install the addon/plugin.

suomi

On 11/11/2016 08:49 AM, Nicolas Kovacs wrote:

Hi,

I just installed a CentOS 7 + KDE desktop in my office's network. So
far, I'm quite happy with the results, though I have some trouble
getting the printer to work. All the other machines in my office
(server, desktops, workstation) are running Slackware64 14.1 or 14.2,
and they can all use the printer perfectly.

I installed hplip-gui and ran it. The printer is a network printer, it
has a static IP in the network and can also be addressed by its hostname.

  [kikinovak@alphamule:~] $ host hp-officejet
  hp-officejet.microlinux.lan has address 192.168.2.252

When I run hp-setup with the default options, the setup program "sees"
the printer, but informs me that there is a "communication problem". I
figure this is because the default seach method is mDNS/Bonjour. I tried
again with the SLP option, and this time the setup procedure went OK. Or
it seemed so, as the test page was blank.

Now what?

A few details about my system: SELinux, IPv6 and firewall are disabled.
CUPS is running OK. I checked on the HP website that this printer
requires HPLIP 3.11.10 or greater, which seems OK, since the HPLIP
version shipping with CentOS is 3.13.something.

Cheers,

Niki


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Relocation of logfiles in logwatch

2016-11-11 Thread adrian
Hi,
I try to teach logwatch that some of my logfiles are relocated. E.g.,
mail mailog now lives in mail/info and secure has moved too auth/info.
I adjusted /etc/logwatch/conf/logfiles/SERVICE.conf accordingly but
logwatch does not understand.
What is the right way to adapt logwatch to the new reality?

Adrian



-- 
Adri P. van Bloois
Antonlaan 104   email:  adr...@pa0rda.nl
3701 VG Zeist   voice:  +31-(0)-30-6912741
The Netherlands fax:NONE

52 05'15.77"N 5 4'44.56"E
QTH-locater  JO 22 OC


"Elegance is not a dispensable luxury but a factor that decides between 
 success and failure."
Edsger W. Dijkstra
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] clamd@amavisd fails under systemd

2016-11-11 Thread Rob Kampen

On 11/11/16 13:36, Gordon Messmer wrote:

On 11/09/2016 02:07 AM, Rob Kampen wrote:

so I have /etc/tmpfiles.d/clamd.amavisd.conf with content
d /var/run/clamd.amavisd 0755 amavis amavis -

the process owner name and group name are amavis
this is not quite what you specified - which should it be?


If "User" is set to amavis in the clamd configuration, that looks fine.

My real head scratch problem is that running clamd from a cli works 
perfectly.
Trying to get systemd (via systemctl start clamd@amavisd.service) 
brings it up but after 1 second removes the pid file and shuts down. 
set up clamd via the service file to use --debug and get nothing helpful
Trying to debug this systemd stuff seems impossible 


systemd starts processes in the correct SELinux context, while running 
it from the shell does not.  So my first guess would be that it's an 
SELinux issue.  Use "setenforce" to put the system in permissive mode 
to see if that's the case.  If so, "grep AVC /var/log/audit/audit.log" 
for more info.
Tried this - set it to permissive and tried the systemctl start 
clamd@amavisd.service and got exactly the same result - tried a number 
of times - no messages in the logs to indicate a problem - just after 
the final start up message of :-

>Self checking every 600 seconds.
after one second we get
>Pid file removed.
>Stopped at Fri Nov 11 04:35:49 2016
>Socket file removed.

So not selinux.
Thanks for the idea - I was unaware that systemd is selinux aware and 
friendly.

I'll keep looking .


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] clamd@amavisd fails under systemd

2016-11-11 Thread Rob Kampen

On 11/11/16 13:36, Gordon Messmer wrote:

On 11/09/2016 02:07 AM, Rob Kampen wrote:

so I have /etc/tmpfiles.d/clamd.amavisd.conf with content
d /var/run/clamd.amavisd 0755 amavis amavis -

the process owner name and group name are amavis
this is not quite what you specified - which should it be?


If "User" is set to amavis in the clamd configuration, that looks fine.

My real head scratch problem is that running clamd from a cli works 
perfectly.
Trying to get systemd (via systemctl start clamd@amavisd.service) 
brings it up but after 1 second removes the pid file and shuts down. 
set up clamd via the service file to use --debug and get nothing helpful
Trying to debug this systemd stuff seems impossible 


systemd starts processes in the correct SELinux context, while running 
it from the shell does not.  So my first guess would be that it's an 
SELinux issue.  Use "setenforce" to put the system in permissive mode 
to see if that's the case.  If so, "grep AVC /var/log/audit/audit.log" 
for more info.

Another random thought
When I invoke from the CLI  - there is a -nofork=yes as a part of the 
invocation.
When systemd tries to do the invocation via the ExecStart line - the 
original clamd@.service file had this --nofork=yes also, the problem was 
that this just caused an abend of the start up with the message:

> /usr/sbin/clamd: unrecognized option `--nofork=yes'
> ERROR: Unknown option passed
> ERROR: Can't parse command line options
and a look at the clamd man shows no such parameter - thus I removed it.
I wonder if this is the issue? Not sure what I can or how I can test.
Will keep playing



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Trouble setting up HP Officejet Pro 8600 printer on CentOS 7 + KDE

2016-11-11 Thread Nicolas Kovacs
Le 11/11/2016 à 09:02, anax a écrit :
> Hi Niki
> don't you need a hplip addon/plugin, which you can fetch from
> http://hplipopensource.com/hplip-web/install/install/index.html
> 
> There, with the wizard, you get a file hplip-3.x.x.run
> which you download and run using
> bash hplip-3.x.x.run
> 
> This will install the addon/plugin.

Thanks, I got it to work indeed. Though there's a special utility called
hp-plugin to do that.

I did some more reading and experimenting, and I have a few general
questions about HPLIP on CentOS.

1. Generally, I have two options. Either go with the 3.13.x HPLIP
packages provided by RHEL/CentOS, or download the more recent (currently
3.16) HPLIP package on the HP site. Which way do you choose to go?

2. If I choose to go with the HP package, should I blacklist the
"official" packages provided by the distribution?

3. On Slackware systems, a normal user must be a member of the 'lp' and
'scanner' groups to be able to use a printer/scanner. How's that in CentOS?

4. Is the proprietary HP plugin printer-specific or only specific to the
installed version of HPLIP?

5. Do I have to run hp-plugin *before* setting up my printer? Curiously
enough, I tried to setup my printer, but there was no automatic prompt
for the plugin download. Had to do it manually.

On a side note, I've always been favoring HP printers for my clients. On
Slackware systems (which I've been using until now) they're a breeze to
setup and work out of the box with HPLIP. Whenever I had some very
recent printers, I just built a package from the latest source, which
was trivial and also worked perfectly.

Cheers,

Niki Kovacs

-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Trouble setting up HP Officejet Pro 8600 printer on CentOS 7 + KDE

2016-11-11 Thread Nicolas Kovacs
Le 11/11/2016 à 12:37, Nicolas Kovacs a écrit :
> 1. Generally, I have two options. Either go with the 3.13.x HPLIP
> packages provided by RHEL/CentOS, or download the more recent (currently
> 3.16) HPLIP package on the HP site. Which way do you choose to go?

Later, after some more testing.

The hplip-gui package provided by RHEL/CentOS doesn't work with this
printer, though it *should*. Theory and practice...

I removed all HPLIP-related stuff and downloaded and installed the
hplipfull package provided by HP on their website. 'yum localinstall'
informed me about a few conflicting residual packages like hplip-libs
and hplip-common on my system. I removed these, and everyting went well.

First thing, I downloaded the plugin:

  # hp-plugin

I got rid of the old (non functional) printer configuration and started
fresh:

  # hp-setup

The printer was added OK, but curiously enough, the test page was
completely blank. I tried to print something else and decided to try the
Firefox home page with the CentOS text. This printed OK.

Curiously enough, KDE's Skanlite application is completely missing from
the repos, so I installed simple-scan. I tried to scan a page, and the
scanner also works perfectly.

So the only remaining problem seems to be: why does the test page button
not work and only print out a blank page?

Cheers,

Niki


-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] httpd-filesystem in 7.3 ??

2016-11-11 Thread Alice Wonder
Does anyone know if the Apache httpd in CentOS 7.3 rebase is going to 
use the httpd-filesystem that Fedora is now using?


I understand it has some advantages to some people with how PHP is run.

I'm not advocating for it I just would like to know as I maintain a 
LibreSSL LAMP stack and need to know if I need to look at the Fedora 
packaging to update my own packaging so I can remain as close to 7.3 
style as reasonably possible.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] ldns-dane

2016-11-11 Thread James B. Byrne
This is an epel package but I thought that I would ask here first.  I
am encountering unexpected behaviour from this program and I would
like to know if it is a bug, or I am configuring something wrong, of
if this is intended behaviour.

ldns-dane version 1.6.16 (ldns version 1.6.16)

When I attempt to specify the entire certificate as the desired data
source for this program I get the following error:

ldns-dane   \
  -n -o 0   \
  -c CA_HLL_ROOT_2016.pem  \
  create harte-lyne.ca 443 \
  2 0 2
 should be in range [0-1]

Likewise I cannot specify the output format as no-hash.

ldns-dane   \
  -n -o 0   \
  -c CA_HLL_ROOT_2016.pem  \
  create harte-lyne.ca 443 \
  2 1 0
 should be in range [0-2]

In fact, 0 is not an accepted value in any of these positions:

ldns-dane   \
  -n -o 0 \
  -c CA_HLL_ROOT_2016.pem  \
 create harte-lyne.ca 443 \
 0 1 1
 should be in range [0-3]

Why is zero invalid?


-- 
***  e-Mail is NOT a SECURE channel  ***
Do NOT transmit sensitive data via e-Mail
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] clamd@amavisd fails under systemd

2016-11-11 Thread Gordon Messmer

On 11/11/2016 02:39 AM, Rob Kampen wrote:
When I invoke from the CLI  - there is a -nofork=yes as a part of the 
invocation.
When systemd tries to do the invocation via the ExecStart line - the 
original clamd@.service file had this --nofork=yes also, the problem 
was that this just caused an abend of the start up with the message:


Not on my system, it doesn't:

$ grep Exec /usr/lib/systemd/system/clamd@.service
ExecStart = /usr/sbin/clamd -c /etc/clamd.d/%i.conf --foreground=yes
$ rpm -qf /usr/lib/systemd/system/clamd@.service
clamav-server-systemd-0.99.2-1.el7.noarch



> /usr/sbin/clamd: unrecognized option `--nofork=yes'
> ERROR: Unknown option passed
> ERROR: Can't parse command line options
and a look at the clamd man shows no such parameter - thus I removed it.
I wonder if this is the issue? Not sure what I can or how I can test. 


Yeah, it might be worth removing the package and reinstalling it. You 
shouldn't need to modify the provided systemd service file.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] clamd@amavisd fails under systemd

2016-11-11 Thread Helmut Drodofsky

CentOS 7 and my experience with clamav 99.2 from epel repository:

instead of --nofork you need --foreground=yes

nofork parameter is definitly outdated.
See
man clamd.conf
and
https://www.centos.org/forums/viewtopic.php?t=58763
with the necessary changes in
/etc/systemd/system/multi-user.target.wants/clamd.service


Best regards

--
Viele Grüße
Helmut Drodofsky
 
Internet XS Service GmbH

Heßbrühlstraße 15
70565 Stuttgart
  Geschäftsführung
Dr.-Ing. Roswitha Hahn-Drodofsky
HRB 21091 Stuttgart
USt.ID: DE190582774
Tel. 0711 781941 0
Fax: 0711 781941 79
Mail: i...@internet-xs.de
www.internet-xs.de

Am 12.11.2016 um 04:46 schrieb Gordon Messmer:

On 11/11/2016 02:39 AM, Rob Kampen wrote:
When I invoke from the CLI  - there is a -nofork=yes as a part of the 
invocation.
When systemd tries to do the invocation via the ExecStart line - the 
original clamd@.service file had this --nofork=yes also, the problem 
was that this just caused an abend of the start up with the message:


Not on my system, it doesn't:

$ grep Exec /usr/lib/systemd/system/clamd@.service
ExecStart = /usr/sbin/clamd -c /etc/clamd.d/%i.conf --foreground=yes
$ rpm -qf /usr/lib/systemd/system/clamd@.service
clamav-server-systemd-0.99.2-1.el7.noarch



> /usr/sbin/clamd: unrecognized option `--nofork=yes'
> ERROR: Unknown option passed
> ERROR: Can't parse command line options
and a look at the clamd man shows no such parameter - thus I removed it.
I wonder if this is the issue? Not sure what I can or how I can test. 


Yeah, it might be worth removing the package and reinstalling it. You 
shouldn't need to modify the provided systemd service file.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] clamd@amavisd fails under systemd - FIXED

2016-11-11 Thread Rob Kampen

On 12/11/16 16:46, Gordon Messmer wrote:

On 11/11/2016 02:39 AM, Rob Kampen wrote:
When I invoke from the CLI  - there is a -nofork=yes as a part of the 
invocation.
When systemd tries to do the invocation via the ExecStart line - the 
original clamd@.service file had this --nofork=yes also, the problem 
was that this just caused an abend of the start up with the message:


Not on my system, it doesn't:

$ grep Exec /usr/lib/systemd/system/clamd@.service
ExecStart = /usr/sbin/clamd -c /etc/clamd.d/%i.conf --foreground=yes
$ rpm -qf /usr/lib/systemd/system/clamd@.service
clamav-server-systemd-0.99.2-1.el7.noarch



> /usr/sbin/clamd: unrecognized option `--nofork=yes'
> ERROR: Unknown option passed
> ERROR: Can't parse command line options
and a look at the clamd man shows no such parameter - thus I removed it.
I wonder if this is the issue? Not sure what I can or how I can test. 


Yeah, it might be worth removing the package and reinstalling it. You 
shouldn't need to modify the provided systemd service file.

this looks like the issue.
doing the rpm -qf /usr/lib/systemd/system/clamd@.service
gave no owner??
So I tried a reinstall and it informed me the package 
clamav-server-systemd-0.99.2-1.el7.noarch was not installed - no idea 
where the systemd service file came from.

So I installed it and it now appears to run.

thanks so much for your assistance - progress finally being made!

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos