[CentOS] CentOS 6 - Support for CanoScan LiDE 210
Hi folks, for some time I used a HP 2840 AiO device, connected via LAN, to scan documents. As scanning application I use xsane. I want to replace that HP scanner by a CanoScan LiDE 210. # LANG="" yum info libsane-hpaio ... Installed Packages Name: libsane-hpaio Arch: x86_64 Version : 3.14.6 Release : 3.el6 Size: 148 k Repo: installed From repo : base Summary : SANE driver for scanners in HP's multi-function devices URL : http://hplip.sourceforge.net/ License : GPLv2+ Description : SANE driver for scanners in HP's multi-function devices (from HPOJ). Now I connected CanoScan LiDE 210 Scanner via USB cable to my CentOS 6 workstation. # dmesg | tail --lines=15 ... usb 3-1: new high speed USB device number 8 using xhci_hcd usb 3-1: New USB device found, idVendor=04a9, idProduct=190a usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-1: Product: CanoScan usb 3-1: Manufacturer: Canon usb 3-1: configuration #1 chosen from 1 choice ... After opening xsane it seems to be connected to the HP Scanner. I can not find any options for choosing another scanner device. From http://www.sane-project.org/sane-mfgs.html I can see that CanoScan LiDE 210 is supported by genesys 1.0-63. From my understanding on CentOS the genesys backend is included in sane-backends: # LANG="" yum info sane-backends ... Installed Packages Name: sane-backends Arch: x86_64 Version : 1.0.21 Release : 3.el6 Size: 4.4 M Repo: installed From repo : anaconda-CentOS-201410241409.x86_64 Summary : Scanner access software URL : http://www.sane-project.org License : GPLv2+ and GPLv2+ with exceptions and Public Domain Description : Scanner Access Now Easy (SANE) is a universal scanner interface. The : SANE application programming interface (API) provides standardized : access to any raster image scanner hardware (flatbed scanner, : hand-held scanner, video and still cameras, frame-grabbers, etc.). The sane-backends is installed, but I can not "see" the scanner: # scanimage -L device `hpaio:/net/HP_Color_LaserJet_2840?zc=NPI9AC264' is a Hewlett-Packard HP_Color_LaserJet_2840 all-in-one I have no idea what I can do now. It is not clear to me if sane-backends package really includes the required genesys 1.0-63 version. Any help to make the new scanner work is appreciated. Regards, Meikel ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 - Support for CanoScan LiDE 210
Am 26.09.2015 um 13:11 schrieb Leon Fauster: Am 26.09.2015 um 12:08 schrieb Meikel: Hi folks, for some time I used a HP 2840 AiO device, connected via LAN, to scan documents. As scanning application I use xsane. I want to replace that HP scanner by a CanoScan LiDE 210. # LANG="" yum info libsane-hpaio ... Installed Packages Name: libsane-hpaio Arch: x86_64 Version : 3.14.6 Release : 3.el6 Size: 148 k Repo: installed From repo : base Summary : SANE driver for scanners in HP's multi-function devices URL : http://hplip.sourceforge.net/ License : GPLv2+ Description : SANE driver for scanners in HP's multi-function devices (from HPOJ). Now I connected CanoScan LiDE 210 Scanner via USB cable to my CentOS 6 workstation. # dmesg | tail --lines=15 ... usb 3-1: new high speed USB device number 8 using xhci_hcd usb 3-1: New USB device found, idVendor=04a9, idProduct=190a usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-1: Product: CanoScan usb 3-1: Manufacturer: Canon usb 3-1: configuration #1 chosen from 1 choice ... After opening xsane it seems to be connected to the HP Scanner. I can not find any options for choosing another scanner device. From http://www.sane-project.org/sane-mfgs.html I can see that CanoScan LiDE 210 is supported by genesys 1.0-63. From my understanding on CentOS the genesys backend is included in sane-backends: # LANG="" yum info sane-backends ... Installed Packages Name: sane-backends Arch: x86_64 Version : 1.0.21 Release : 3.el6 Size: 4.4 M Repo: installed From repo : anaconda-CentOS-201410241409.x86_64 Summary : Scanner access software URL : http://www.sane-project.org License : GPLv2+ and GPLv2+ with exceptions and Public Domain Description : Scanner Access Now Easy (SANE) is a universal scanner interface. The : SANE application programming interface (API) provides standardized : access to any raster image scanner hardware (flatbed scanner, : hand-held scanner, video and still cameras, frame-grabbers, etc.). The sane-backends is installed, but I can not "see" the scanner: # scanimage -L device `hpaio:/net/HP_Color_LaserJet_2840?zc=NPI9AC264' is a Hewlett-Packard HP_Color_LaserJet_2840 all-in-one I have no idea what I can do now. It is not clear to me if sane-backends package really includes the required genesys 1.0-63 version. Any help to make the new scanner work is appreciated. is it enabled in dll.conf ? As far as I can see, it is enabled there: # grep genesys /etc/sane.d/dll.conf genesys ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 - Support for CanoScan LiDE 210
Am 26.09.2015 um 12:08 schrieb Meikel: > Hi folks, > > for some time I used a HP 2840 AiO device, connected via LAN, to scan > documents. As scanning application I use xsane. I want to replace that HP > scanner by a CanoScan LiDE 210. > > # LANG="" yum info libsane-hpaio > ... > Installed Packages > Name: libsane-hpaio > Arch: x86_64 > Version : 3.14.6 > Release : 3.el6 > Size: 148 k > Repo: installed > From repo : base > Summary : SANE driver for scanners in HP's multi-function devices > URL : http://hplip.sourceforge.net/ > License : GPLv2+ > Description : SANE driver for scanners in HP's multi-function devices (from > HPOJ). > > Now I connected CanoScan LiDE 210 Scanner via USB cable to my CentOS 6 > workstation. > > # dmesg | tail --lines=15 > ... > usb 3-1: new high speed USB device number 8 using xhci_hcd > usb 3-1: New USB device found, idVendor=04a9, idProduct=190a > usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > usb 3-1: Product: CanoScan > usb 3-1: Manufacturer: Canon > usb 3-1: configuration #1 chosen from 1 choice > ... > > After opening xsane it seems to be connected to the HP Scanner. I can not > find any options for choosing another scanner device. From > http://www.sane-project.org/sane-mfgs.html I can see that CanoScan LiDE 210 > is supported by genesys 1.0-63. From my understanding on CentOS the genesys > backend is included in sane-backends: > > # LANG="" yum info sane-backends > ... > Installed Packages > Name: sane-backends > Arch: x86_64 > Version : 1.0.21 > Release : 3.el6 > Size: 4.4 M > Repo: installed > From repo : anaconda-CentOS-201410241409.x86_64 > Summary : Scanner access software > URL : http://www.sane-project.org > License : GPLv2+ and GPLv2+ with exceptions and Public Domain > Description : Scanner Access Now Easy (SANE) is a universal scanner > interface. The >: SANE application programming interface (API) provides > standardized >: access to any raster image scanner hardware (flatbed scanner, >: hand-held scanner, video and still cameras, frame-grabbers, > etc.). > > The sane-backends is installed, but I can not "see" the scanner: > > # scanimage -L > device `hpaio:/net/HP_Color_LaserJet_2840?zc=NPI9AC264' is a Hewlett-Packard > HP_Color_LaserJet_2840 all-in-one > > I have no idea what I can do now. It is not clear to me if sane-backends > package really includes the required genesys 1.0-63 version. > > Any help to make the new scanner work is appreciated. is it enabled in dll.conf ? -- LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 - Support for CanoScan LiDE 210
On Sat, Sep 26, 2015 at 3:08 AM, Meikelwrote: > scanner by a CanoScan LiDE 210. > Installed Packages > Name: sane-backends > Arch: x86_64 > Version : 1.0.21 > I have no idea what I can do now. It is not clear to me if sane-backends > package really includes the required genesys 1.0-63 version. You need sane-backends 1.0.22 or later to have genesys 1.0-63. There are a few ways to install a newer version of sane-backends on EL6. One is to rebuild a src.rpm from Fedora. The other is to use the linuxtech-backports repo [1]. I have even built it from a tarball but this should not be necessary. If you need more assistance, let us know. Akemi [1] http://pkgrepo.linuxtech.net/el6/backports/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems with my touchpad in CentOS7
On Fri, Sep 25, 2015 at 11:12 AM, C.L. Martinezwrote: > On 09/25/2015 04:32 PM, Akemi Yagi wrote: >> >> On Fri, Sep 25, 2015 at 9:02 AM, C.L. Martinez >> wrote: >>> I have a lot of errors like this: >>> >>> psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 >>> >>> This is a CentOS7 laptop (fully patched). It is the same problem >>> reported >>> here: >>> >>> https://bugs.centos.org/view.php?id=4192 >> I had a quick look at the code in the current CentOS-7 kernel. The >> patch referenced in bug #4192 is included in CentOS 7. What is your >> hardware? >> > > It is an Acer TravelMate TMP255-M I was not able to confirm that this particular model is supported. I understand you see the errors but is the mouse/touchpad actually working? If this is a problem with the psmouse module, you could try reloading it: modprobe -r psmouse modprobe psmouse Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 - Support for CanoScan LiDE 210
On Sat, 26 Sep 2015 12:08:02 +0200 Meikel wrote: > I want to replace that > HP scanner by a CanoScan LiDE 210. http://www.melvilletheatre.com/articles/canon-lide-110-scanner/ -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba Enterprise from Sernet no longer free
On Mon, 21 Sep 2015, Robert Moskowitz wrote: http://www.samba.plus/ Currently this, other than rolling your own, this appears the only way to have a Samba AD on Centos. For the time being you can still get samba 4.2 packages and run Samba AD on Centos @ https://portal.enterprisesamba.com. The paid service is only for 4.3+ so you should be good for a while. HTH, Regards, -- Tom m...@tdiehl.org Spamtrap address me...@tdiehl.org ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-virt] CentOS 6 Xen virt* issues
Hello, I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and dom0 3.18.17 rpms, and noticed these new problems: 1) virt-manager fails to start with an error: "D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory" And indeed.. there was no such file. Running command "dbus-uuidgen --ensure" fixed it, and virt-manager starts OK after that. So this was more for the mailinglist archives, if someone else meets the same issue. 2) virt-viewer doesn't work anymore. It seems in el6.6 virt-viewer was version 0.6.0-11, but now in el6.7 it's 2.0-7, with a lot of changes.. If I try to use virt-viewer and run "virt-viewer " command, I get an error popup dialog saying "Failed to connect: Display can only be attached through libvirt with --attach". verbose debug output: # virt-viewer -v --debug -c "xen://" testvm (virt-viewer:9420): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 [root@fdell01 rpm]# less testvm01.txt (virt-viewer:9374): virt-viewer-DEBUG: connecting ... (virt-viewer:9374): virt-viewer-DEBUG: Opening connection to libvirt with URI xen:// Opening connection to libvirt with URI xen:// (virt-viewer:9374): virt-viewer-DEBUG: Add handle 7 1 0x865520 (virt-viewer:9374): virt-viewer-DEBUG: initial connect (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f (virt-viewer:9374): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212 (virt-viewer:9374): virt-viewer-DEBUG: No guest-specific fullscreen config, using fallback (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm is running, determining display Guest testvm is running, determining display (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm has a vnc display Guest testvm has a vnc display (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only access prevents virDomainOpenGraphics (virt-viewer:9374): virt-viewer-DEBUG: After open connection callback fd=-1 (virt-viewer:9374): virt-viewer-DEBUG: Remove handle 1 7 (virt-viewer:9374): virt-viewer-DEBUG: Disposing window 0x7e1820 (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 And trying with the "attach" option: # virt-viewer -v --debug -c "xen://" -a testvm (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 [root@fdell01 rpm]# less testvm02.txt (virt-viewer:9389): virt-viewer-DEBUG: connecting ... (virt-viewer:9389): virt-viewer-DEBUG: Opening connection to libvirt with URI xen:// Opening connection to libvirt with URI xen:// (virt-viewer:9389): virt-viewer-DEBUG: Add handle 7 1 0x13ef580 (virt-viewer:9389): virt-viewer-DEBUG: initial connect (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000 (virt-viewer:9389): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212 (virt-viewer:9389): virt-viewer-DEBUG: No guest-specific fullscreen config, using fallback (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000 (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm is running, determining display Guest testvm is running, determining display (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm has a vnc display Guest testvm has a vnc display (virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection (virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing is not supported by this connection (virt-viewer:9389): virt-viewer-DEBUG: After open connection callback fd=-1 (virt-viewer:9389): virt-viewer-DEBUG: Remove handle 1 7 (virt-viewer:9389): virt-viewer-DEBUG: Disposing window 0x136b820 (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: (null),(null),(null),-1,(null),(null),(null),0 So it seems both connection types/methods now fail.. I'm not sure if the issue is in our custom libvirt build, or in Xen's qemu.. (googling for those errors reveals some related patches which also have patches for qemu: http://comments.gmane.org/gmane.comp.emulators.virt-tools/9185) Error from the first attempt: (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only access prevents virDomainOpenGraphics Error from the second attempt: (virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection (virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing is not
Re: [CentOS] CentOS 6 - Support for CanoScan LiDE 210
On Sat, Sep 26, 2015 at 09:55:17AM -0600, Frank Cox wrote: > On Sat, 26 Sep 2015 12:08:02 +0200 > Meikel wrote: > > > I want to replace that > > HP scanner by a CanoScan LiDE 210. > > http://www.melvilletheatre.com/articles/canon-lide-110-scanner/ To the original poster: I followed Frank's procedure on my C6 system, a year or two ago, and it works fine for my LiDE 210. -- Fred Smith -- fre...@fcshome.stoneham.ma.us - God made him who had no sin to be sin for us, so that in him we might become the righteousness of God." --- Corinthians 5:21 - ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-virt] CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing
On Tue, Sep 22, 2015 at 12:08:12PM +0100, George Dunlap wrote: > > > Anyway, here's something I noticed while testing xend bits: > > > > # systemctl enable xend.service > > xend.service is not a native service, redirecting to /sbin/chkconfig. > > Executing /sbin/chkconfig xend on > > The unit files have no [Install] section. They are not meant to be enabled > > using systemctl. > > Possible reasons for having this kind of units are: > > 1) A unit may be statically enabled by being symlinked from another unit's > >.wants/ or .requires/ directory. > > 2) A unit's purpose may be to act as a helper for some other unit which has > >a requirement dependency on it. > > 3) A unit may be started when needed via activation (socket, path, timer, > >D-Bus, udev, scripted systemctl call, ...). > > > > > > "systemctl start xend.service" works OK though.. and after that xm works > > too. > > Right -- I haven't tried xend under systemd. Given that xend is gone > in 4.6, I'm considering whether to say "patches welcome" re fixing > xend in 4.4 for C7... > I'll try to investigate.. Thanks, -- Pasi > -George ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS] Is this a bug in CentOS-7 BackupPC?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/09/15 16:16, Timothy Murphy wrote: > When I try to start BackupPC with "sudo systemctl restart > backuppc" on my CentOS-7 server (running kernel > 3.10.0-229.14.1.el7.x86_64) I get the following error in > /var/log/BackupPC/LOG > > 2015-09-26 13:58:14 Reading hosts file 2015-09-26 13:58:14 unix > bind() failed: No such file or directory > > This message occurs in the Perl script > /usr/share/BackupPC/bin/BackupPC : > > my $sockFile = "/var/run/BackupPC/BackupPC.sock"; > unlink($sockFile); if ( !bind(SERVER_UNIX, sockaddr_un($sockFile)) > ) { print(LOG $bpc->timeStamp, "unix bind() failed: $!\n"); > exit(1); } > > As far as I can see (I'm no guru) this is trying to open a unix > socket with the name /var/run/BackupPC/BackupPC.sock . > > There is no directory /var/run/BackupPC/ on my server. When I > create this, setting backuppc.apache as owner, and run "sudo > systemctl restart backuppc" I see in /var/log/BackupPC/LOG that > BackupPC has (at long last) started > Seems a packaging issue ? From where is your rpm for backuppc coming ? /var/run on EL7 is in fact pointing to /run , which is tmpfs, so packages aren't supposed to drop something there directly, or that will be gone anyway next time your restart the machine. Workaround for those not-yet-fixed-for-systemd-packages : man tmpfiles.d (that will create/maintain those) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYG3LUACgkQnVkHo1a+xU4P3wCgkVddXAtL48uYgTmchMOZGbLl d9MAn2Vn7ZRPVz/UwtjhisfhMJE+JiLU =dvYX -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-virt] CentOS 6 Xen virt* issues
On Sat, Sep 26, 2015 at 09:04:23PM +0300, Pasi Kärkkäinen wrote: > Hello, > > I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and > dom0 3.18.17 rpms, and noticed these new problems: > And third issue aswell: 3) Creating an HVM guest using virt-manager with file-based storage uses loopback-mount, not blktap When I manually create a new Xen HVM guest using virt-manager, and choose file-based image for storage of the VM, it seems to be set up to use file: backend/driver with loopback-mounted image file: # losetup -a /dev/loop0: [fd00]:1709109 (/var/lib/libvirt/images/testvm2.img) With earlier versions of rpms similar setup used blktap2 backend.. (and yes, I do have blktap module loaded in dom0 kernel). Thanks, -- Pasi ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS] Is this a bug in CentOS-7 BackupPC?
When I try to start BackupPC with "sudo systemctl restart backuppc" on my CentOS-7 server (running kernel 3.10.0-229.14.1.el7.x86_64) I get the following error in /var/log/BackupPC/LOG 2015-09-26 13:58:14 Reading hosts file 2015-09-26 13:58:14 unix bind() failed: No such file or directory This message occurs in the Perl script /usr/share/BackupPC/bin/BackupPC : my $sockFile = "/var/run/BackupPC/BackupPC.sock"; unlink($sockFile); if ( !bind(SERVER_UNIX, sockaddr_un($sockFile)) ) { print(LOG $bpc->timeStamp, "unix bind() failed: $!\n"); exit(1); } As far as I can see (I'm no guru) this is trying to open a unix socket with the name /var/run/BackupPC/BackupPC.sock . There is no directory /var/run/BackupPC/ on my server. When I create this, setting backuppc.apache as owner, and run "sudo systemctl restart backuppc" I see in /var/log/BackupPC/LOG that BackupPC has (at long last) started -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Is this a bug in CentOS-7 BackupPC?
Fabian Arrotin wrote: >> This message occurs in the Perl script >> /usr/share/BackupPC/bin/BackupPC : >> >> my $sockFile = "/var/run/BackupPC/BackupPC.sock"; >> unlink($sockFile); if ( !bind(SERVER_UNIX, sockaddr_un($sockFile)) >> ) { print(LOG $bpc->timeStamp, "unix bind() failed: $!\n"); >> exit(1); } >> >> As far as I can see (I'm no guru) this is trying to open a unix >> socket with the name /var/run/BackupPC/BackupPC.sock . >> >> There is no directory /var/run/BackupPC/ on my server. When I >> create this, setting backuppc.apache as owner, and run "sudo >> systemctl restart backuppc" I see in /var/log/BackupPC/LOG that >> BackupPC has (at long last) started >> > > Seems a packaging issue ? From where is your rpm for backuppc coming ? >From epel . > /var/run on EL7 is in fact pointing to /run , which is tmpfs, so > packages aren't supposed to drop something there directly, or that > will be gone anyway next time your restart the machine. > Workaround for those not-yet-fixed-for-systemd-packages : man > tmpfiles.d (that will create/maintain those) I don't really understand this. The perl script wants to create /var/run/BackupPC/BackupPC.sock which it seems it cannot do unless /var/run/BackupPC/ exists. If as you say this disappears on re-booting, I don't see how this program could work. -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Is this a bug in CentOS-7 BackupPC?
On Sat, Sep 26, 2015 at 08:12:40PM +0100, Timothy Murphy wrote: > I don't really understand this. > The perl script wants to create /var/run/BackupPC/BackupPC.sock > which it seems it cannot do unless /var/run/BackupPC/ exists. > If as you say this disappears on re-booting, > I don't see how this program could work. Seems like a packaging bug in EPEL. Fedora does this (semi-)right, by dropping down an /etc/tmpfiles.d/BackupPC.conf, which instantiates the /var/run/BackupPC directory as 0755 root:backuppc. Looking at the epel7 specfile, I see: # tmpfiles.d & systemd support in all supported Fedora now, but not RHEL %if 0%{?fedora} %global _with_tmpfilesd 1 %global _with_systemd 1 %endif and then later: %if 0%{?_with_tmpfilesd} install -d $RPM_BUILD_ROOT/%{_sysconfdir}/tmpfiles.d install -p -m 0644 %{SOURCE6} $RPM_BUILD_ROOT/%{_sysconfdir}/tmpfiles.d/%{name}.conf %endif and %if 0%{?_with_tmpfilesd} %config(noreplace) %{_sysconfdir}/tmpfiles.d/%{name}.conf %endif Of course, CentOS7 (and RHEL7) supports tmpfiles.d, in fact, may system services require it, such as cups, samba, pam, etc. I'm not sure why the BackupPC package installs it in /etc/tmpfiles.d instead of /usr/lib/tmpfiles.d, probably because the person who made the package isn't very systemd-saavy. The contents of the /etc/tmpfiles.d/BackupPC.conf file looks like this: D /var/run/BackupPC 0775 root backuppc - If you create that file, you'll get the /var/run/BackupPC file when you start up. I suggest filing a bug against the EPEL package if you want to get it fixed there. -- Jonathan Billings___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos