similar to: Re: [Fedora-xen] Virt-manager does not connect to libvirt/Xen? Xen 4.1.5 installed from source on Fedora 17.

I want to get couple of DomUs running with Xen. I installed Xen 4.1.5 from source on a Fedora 17 Dom0. I did some reading on configuring DomUs using xl/xm and cfg files. http://www.fclose.com/b/linux/2544/setting-up-lvm-backed-xen-domu/ http://www.fclose.com/w/Setting_Up_Xen_DomU_on_Fedora:_Unmodified_Fedora_on_Top_of_Xenified_Fedora_Xen_Dom0%23Install_Fedora_12_Linux_via_Internet So basically I

Dear samba-Team, The bug reported in PR#12819 for AXI 4.1.5 persits also in samba 2.0.3. The Bug prevents the connecting of other users as root to any share. I have a workaround/fix tested on AIX 4.1.5 ,4.3.2 with gcc 2.8.1 here: Change samba-2.0.3/source/lib/util_sec.c funktion set_effective_uid like this: 155c155 < #elif defined(HAVE_SETREUID) --- > #elif defined(HAVE_SETREUID)

Hi @all, experimenting with 4.1.5 and printing I have messages like this in the log: spoolss_connect_to_client: machine X didn't negotiate NT protocol. machine X is a windows 7 machine. I have following definitions in smb.conf: lanman auth = yes client lanman auth = yes client plaintext auth = yes client ntlmv2 auth = no max protocol = SMB3 # <--------------- min

I'm about to do some testing with a an OSX 10.9 client connected to sernet samba 4.1.5 to see what things work and don't both from the finder and from the terminal with unix extensions = yes and no. Does anyone know of any show stopping issues that occur with unix extensions = yes and the latest samba (or 3.6.x, or 4.0.x a) and the latest OSX (or latest update with 10.7 & 10.8)?

Hello, I have a samba 4.1.5. I have created OUs and linked GPO to OU for account lockout policies. Account Lockout Duration: 15min Account Lockout Threshold: 5 invalid attempts Reset Account lockout counter after: 15min I have created a test account and logged in with an incorrect password more than 5 times to a machine. but the test account never locks and the computer never prompts me that

I require urgent assistance on a problem I am having with Samba 1.9.18 on AIX 4.1.5. It seems that upon make install the /usr/local/samba/var/locks directory is not created and upon setting up inetd.conf and executing a kill -1 {pid of inetd} the locks directory still does not exist, no log files are created and STATUS..LCK is not created. I execute start -->run --->\\{system name} I get

Can anyone help with the following problem I am having on AIX 4.1.5. First I compile the code and all compiles with out error or warning then I begin to execute smbstatus, of course I have my smb.conf file. I get an error regarding "Can't read /var/locks/STATUS..LCK". After which I touch that file and then I run smbstatus again and I get the following error: # smbstatus doing

I've been trying to compile Samba 2.0.6 on an RS/6000 J30 running AIX 4.1.5 using gcc 2.95.1. Basically, when I run 'make', every file that it attempts to compile returns the same warning, involving 'struct statfs' in /usr/include/sys/vfs.h I've listed the beginning and end of the output, but didn't think it worth including the whole lot as it's an identical

=================================================================== "I know a lot about cars, man. I can look at any car's headlights and tell you exactly which way it's coming." Mitch Hedberg =================================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.1.

=================================================================== "I know a lot about cars, man. I can look at any car's headlights and tell you exactly which way it's coming." Mitch Hedberg =================================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.1.

Hello, I posted this yesterday to the Xen-devel list, posting it additionally to the fedoraproject list too. My problem is Virt-manager is unable to connect to the hypervisor (explained below). However, xm list, xm info work fine. So I followed the guide http://wiki.xen.org/wiki/Xen_4.2_Build_From_Source_On_RHEL_CentOS_Fedora and built/installed Xen from source, using grub2-mkconfig to rebuild

All, aiming at releases later this or early next week, please test! Thanks, Jan

All, aiming at releases with once again not too many more RCs, please test! Thanks, Jan

Hi. I have problem like this, but on Samba 4.1.11. Any solution? -- Pozdrawiam. Grzegorz Ciesielski grzegorz.ciesielski at budikom.net budikom.net sp. z o.o. sp.k. ul. Trzy Lipy 3, 80-172 Gda?sk NIP: 9571070903 tel.: +48 58 58 58 708 email: biuro at budikom.net

Hi all, At the pre-big thanks to the SAMBA team for many years the great work. Sorry for my english. A week ago, have implemented productively Samba 4.1.5 on CentOS 6.5. I installed samba by default dns server built-in (internal) with the rfc2307. Everything works great, but after a while I noticed that the memory on my server is largely occupied. At this time there are about 10 users domain -

Need Help with this one ASAP! When I issue smbstatus I get the following error: doing parameter max log size = 50 Processing section "[mytest]" doing parameter browseable = yes doing parameter read only = no doing parameter path = / Processing section "[homes]" doing parameter browseable = yes doing parameter guest ok = no doing parameter read only = no doing parameter create

I've got a CTDB 2.5.2 Samba 4.1.5 cluster where I'm seeing smbd processes using too much CPU after the client connection is closed. Doing a truss against the smbd processes shows nothing during this time, so no syscalls seem to be involved. I rebuilt with debug enabled and took stack traces from an offending process spaces about 1 minute apart. Can anyone from the team tell me if

I'm trying to add schema extensions to my Samba (4.1.5) server, as per > https://wiki.samba.org/index.php/Samba4/Schema_extenstions However, importing the example file (after replacing the DOMAIN_TOP_DN) fails: > $ ldbmodify -H sam.ldb /tmp/automount.ldif --option="dsdb:schema update allowed"=true > Unable to find attribute automountMapName in the schema > ERR:

Hi all, I currently have 5 DC's all running 4.1.5 and would like to upgrade them to 4.1.11. Should I upgrade the FSMO DC first and then the others or perhaps the other way around? Can anyone see any pitfalls here? Also, should I just: 1. stop samba 2. ./conffigure && make && make install 3. restart samba ? I am also planning on switching to BIND_DLZ (currently running

Hi, I''ve still have problems with ACPI(?) on Xen. After some system startup or resume CPU temperature goes high although all domUs (and dom0) are idle. On "good" system startup it is about 50-55C, on "bad" - above 67C (most time above 70C). I''ve noticed difference in C-states repored by Xen (attached files). On "bad" startups in addition suspend