similar to: smbd write failure, kernel

Hello, I was using CentOS 5.5 as a "playground" VM at my WinXP notebook and now I'm migrating to a new CentOS 5.6 install and everything has worked well - except samba. I have this very permissive config to export my ~/src dir: # cat /etc/samba/smb.conf [global] guest ok = yes guest account = afarber security = share hosts allow = 172.16.6. 127.0.0.1 [src]

Hey, I'm having problems with samba. It has never worked properly on my server since I've had it installed.. Its for a home server, running xbox-Linux Fedora Core 6. I've just uninstalled every trace of the old samba, and started a fresh. With the latest samba sources I found on the website. The nmbd starts fine, but smbd never starts, and in the kernel log, I get the following

I have recently been told I will have to maintain some CentOS servers at work. Since I have only been using Slackware for the last 16 years, I decided to install CentOS on one of my servers at home to get an idea of the differences. I installed CentOS 5.4 from CD with no problems, did a yum update, set up a couple of samba shares and started to copy over some files from one of my other

I have setup a Samba4 server and would like to report my experiences in the hope that it may be helpful to others. I basically followed the official Samba4 HowTo, which is very good. Based on what I have seen, this is the only document I would recommend people to follow. I will try not to repeat things that are covered in the HowTo, but rather focus on what I did differently or additionally,

Hello, I have Samba 4 installed with some correctly configured shares so I can access them from my Windows box. It is a proven setup from an older Fedora+Samba setup, though on that other machine I have SELinux disabled. So I set samba_export_all_rw=1 to be able to access the shares whose files and directories are labelled public_content_rw_t by issuing: semanage fcontext -a -t

Hey all... not exactly an SELinux veteran, but am trying to work through some issues. Specifically, setting up a simple Samba configuration on a CentOS 5 machine. Determined I needed to do setsebool -P samba_enable_home_dirs 1 In order to get access to home directory shares working correctly. Fine; this is documented in samba_selinux(8). However, I still see the following in my

Hi I have a customer who is having a problem with Samba password changes. The samba server (server12) is set up as a PDC for a WIndows domain with XP clients. Samba is Version 3.0.26a-SerNet-RedHat. OS is Centos 3.9. There is also a separate mail server (server56) running FC6 which uses NIS for user validation. NIS server is running on server12. Generally speaking, everything is working and

2011/6/27 Frederic BOHE <fbohe-guest at alioth.debian.org> > Author: fbohe-guest > Date: Mon Jun 27 13:56:51 2011 > New Revision: 3060 > URL: http://trac.networkupstools.org/projects/nut/changeset/3060 > > Log: > Add NUT server scan. > > (...) > device_t * scan_snmp(char * start_ip, char * stop_ip,long usec_timeout, > snmp_security_t * sec); > >

Hi I have problem connecting with windows XP clients to a sub directory The subdirectory is setup as follows in die smb.conf [wwwshare] comment = www share path = /var/www/html valid users = wwwuser public = no writable = yes printable = no create mask = 0765 I have user level security. The wwwuser is the owner of the html dir. The wwwuser is also the owner of the www

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 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

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

I must have something configured wrong somewhere. I''ve enabled proxy-arp on my shorewall 2.0.7 firewall. Works fine for what its supposed to do, I can see all the machines through it great. However, whenever its enabled, the network on the DMZ goes screwy. I''ve narrowed it down to this: when proxy arp is enabled for that interface, like such: echo 1 >

http://bugs.freedesktop.org/show_bug.cgi?id=13815 Summary: Wrong url for http get Product: swfdec Version: git Platform: Other URL: http://www.betterworldbooks.com/Flash/output.swf OS/Version: All Status: NEW Severity: normal Priority: medium Component: library AssignedTo: swfdec at

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

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, I'm running Dovecot 2.0.13 on my Ubuntu10.04. It's working very well but I faced a problem with Redirect and Vacation using Sieve. :-( In fact, after well configuring the system I dont't receive the redirect message, and in the log I found: ######################################################################################## Jun 9 18:49:37 box7 dovecot: lmtp(10734, user at

https://bugs.freedesktop.org/show_bug.cgi?id=111213 Bug ID: 111213 Summary: VA-API nouveau SIGSEGV and asserts Product: Mesa Version: 19.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

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 ---