similar to: [nut-commits] svn commit r3060 - branches/nut-scanner/tools/nut-scanner

I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good after upgrade until reboot. When rebooted to container I'm getting the following errors.. Any help would be greatly appreciated /bin/mknod: `/dev/lp2': Operation not permitted /bin/chown: cannot access `/dev/lp2': No such file or directory /bin/mknod: `/dev/lp3': Operation not permitted /bin/chown: cannot

On Wed, 2011-09-14 at 12:25 +0000, Charles Lepple wrote: > Author: clepple-guest > Date: Wed Sep 14 12:25:03 2011 > New Revision: 3226 > URL: http://trac.networkupstools.org/projects/nut/changeset/3226 > > Log: > Include <string.h> for nut-scanner > > Modified: > trunk/tools/nut-scanner/scan_snmp.c > trunk/tools/nut-scanner/scan_usb.c > >

Hello! I have samba 3.0.23c-2 installed on Fedora Core 7. Smbd and nmbd daemons start automotically with computer via commands in rc.local: smbd -D nmbd -D But there is one problem. When smbd starts via rc.local, it can't write files to the disk. And when I start it myself, everything is fine. smbd.log: [2007/05/21 09:49:06, 0] lib/util_sock.c:write_data(562) write_data: write failure

Hi when I turn on my PC I able to load the drivers and start my card, if I reboot the PC I have the following error ztcfg -vvv Zaptel Configuration ====================== Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) Channel 03: FXS Kewlstart (Default) (Slaves: 03) Channel 04: FXS Kewlstart (Default) (Slaves: 04) 4 channels

I run a sshd host solely to allow employees to tunnel secure connections to our internal hosts. Some of which do not support encrypted protocols. These connections are chroot'ed via the following in /etc/ssh/sshd_config Match Group !wheel,!xxxxxx,yyyyy AllowTcpForwarding yes ChrootDirectory /home/yyyyy X11Forwarding yes Where external users belong to group yyyyy (primary). We

Hello! I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it). FreeBSD 6.3-STABLE was running fine on it, but I decided to update the machine to 9.1-STABLE. Well, neither my own custom kernel, nor even the official 9.1-RELEASE CD1 would boot... In both cases the boot process runs up to detecting uhub0, then either hangs forever or shuts off after a short while. Again, I thought I

http://bugs.freedesktop.org/show_bug.cgi?id=21257 Summary: Qt applications strange behavior Product: xorg Version: 7.4 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: luizluca at

On Fri, Nov 14, 2014 at 07:32:46PM +0000, mallu mallu wrote: > I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good after upgrade until reboot. When rebooted to container I'm getting the following errors.. Any help would be greatly appreciated > /bin/mknod: `/dev/lp2': Operation not permitted > /bin/chown: cannot access `/dev/lp2': No such file or

Daniel P. Berrangé <berrange@redhat.com> writes: > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> Hi, >> > >> I've met two situations with NVDIMM support in libvirt where I'm not >> sure all the parties (libvirt & I) do the things correctly. >> >> The first problem is with memory alignment and size changes. In

Milan Zamazal <mzamazal@redhat.com> writes: > Daniel P. Berrangé <berrange@redhat.com> writes: > >> On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >>> The second problem is that a VM fails to start with a backing NVDIMM in >>> devdax mode due to SELinux preventing access to the /dev/dax* device (it >>> doesn't happen with any

Navigation Bar March-September 2003 Status Report Introduction: The FreeBSD Bi-monthly status reports are back! In this edition, we catch up on seven highly productive months and look forward to the end of 2003. As always, the FreeBSD development crew has been hard at work. Support for the AMD64 platform quickly sprang up and is nearly complete.

Hello, The Xen community is working on a new virtualization mode (or maybe I should say an extension of HVM) to be able to run PV guests inside HVM containers without requiring a device-model (Qemu). One of the advantages of this new virtualization mode is that now it is much more easier to port guests to run under it (as compared to pure PV guests). Given that FreeBSD already supports

Starting udev: /sbin/restorecon set context /dev/.initramfs/live->system_u:object_r:device_t:s0 failed:'Read-only file system' Resolves: rhbz#675868 Signed-off-by: Mike Burns <mburns at redhat.com> --- recipe/common-post.ks | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/recipe/common-post.ks b/recipe/common-post.ks index a17e899..cf5bc72 100644 ---

Hi A few days ago we rebooted a server and found that one of the Logical Volumes would not mount at boot, but mounted cleanly manually. So I traced the problem to SE Linux. Specifically the context for /dev/mapper/VolGroup01-lv_ staff is wrong. s -lsahZ /dev/mapper/VolGroup01-* lrwxrwxrwx. root root system_u:object_r:quota_db_t:s0 /dev/mapper/VolGroup01-lv_staff -> ../dm-25 lrwxrwxrwx. root

Just installed 7.2, and I'm seeing this - is this a bug in the policy? ************************** SELinux is preventing systemd-readahe from add_name access on the directory .readahead.new. ***** Plugin catchall_labels (83.8 confidence) suggests ******************* If you want to allow systemd-readahe to have add_name access on the .readahead.new directory Then you need to change the

On Sep 24, 2011, at 3:54 PM, clepple+buildbot at ghz.cc wrote: > The Buildbot has detected a new failure of FreeBSD-x86 on Network > UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/FreeBSD-x86/builds/266 http://buildbot.ghz.cc/public/nut/builders/FreeBSD-x86/builds/266/steps/compile/logs/stdio : libtool: compile: gcc

> > The Buildbot has detected a new failure of Ubuntu-maverick-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/32 > > Buildbot URL: http://buildbot.networkupstools.org/public/nut/ > > Buildslave for this Build: cayenne Fred, I had a few spare cycles and tried building

Hi all, Over the last month or so I've installed FreeBSD 9 (-stable) on several Mac Minis via the memstick image; they seem to be pretty good little boxes for things like offsite secondary nameservers, for example, and they're easily replaced in case of problems. However, the newest minis have slightly different hardware, and FreeBSD can't find the built-in NIC. pciconf -lv on the

Citeren Frederic BOHE <fbohe-guest at alioth.debian.org>: > Modified: branches/nut-scanner/tools/nut-scanner/scan_snmp.c > ============================================================================== > --- branches/nut-scanner/tools/nut-scanner/scan_snmp.c Fri Jun 17 > 08:12:00 2011 (r3047) > +++ branches/nut-scanner/tools/nut-scanner/scan_snmp.c Tue Jun 21 >

These patches update the example FLASK policy shipped with Xen and enable its build if the required tools are present. The third patch requires rerunning autoconf to update tools/configure. [PATCH 1/3] flask/policy: sort dom0 accesses [PATCH 2/3] flask/policy: rework policy build system [PATCH 3/3] tools/flask: add FLASK policy to build