similar to: migrating samba to different machine

After reading through the documentation, I realized that as a part of the migration process from Samba-2.2.X to Samba-3.0.0 I needed to convert everyone in my smbadmin group (previously domain admin group = @smbadmin) to the "Domain Admins" group w/rid=512. So, I issued the following command: [root@localhost profile]# net groupmap modify ntgroup="Domain Admins"

µë-

I have a couple questions that I will submit separately. When I have IPchains running I can't get my samba box to show up in network neighborhood, but when I turn ipchains off the box shows up. What rules do I need to add for things to work properly? -- Raymond Norton Little Crow Telemedia Network 320-234-0270

Hello, I just narrowed down an rsync command that keeps failing to the --delete flag: rsync -vv --delete --backup-dir=backup_target --archive /etc myuser@localhost: It gives the following output: ... backup_dir is --delete/ building file list ... done Invalid file index: 1868985864 (count=0) [receiver] delta-transmission enabled rsync error: protocol incompatibility (code 2) at sender.c(189)

In the past, I had restricted rsync so that the -e option was disallowed. As of rsync-3.0.0, I'm now seeing the following requests being made (on the server side): rsync --server -vlogDtprze.iL . I want to prevent '-e' as a client side option so arbitrary programs can't be executed. I found the following, but didn't trace through to verify exactly where I was in the code

[username@localhost source]# ./configure --with-fhs --prefix=/usr --sysconfdir=/etc --with-privatedir=/etc/samba --with-lockdir=/var/state/samba --localstatedir=/var --with-netatalk --with-smbmount --with-pam --with-syslog --with-sambabook --with-utmp --with-acl-support > ~/myconfig.out 2>&1 [username@localhost source]# cat ~/myconfig.out | grep acl checking for sys/acl.h... yes

I work for a school dist, and I am having a bit of trouble with the "Student Server" We have about 3000 students all with their own accounts. I had the samba server setup to share their home directories but their home directories are the same as their login name. So jamie.mcparland would be an example of a share name. But in Win 9X it gets truncated to jamie.mcparla then we get the error

Hello OpenSSH Developers and Community, wolfSSL (formerly known as CyaSSL) is a dual licensed SSL/TLS implementation specializing in the embedded space. As we have grown we are being used in larger systems due to our reduced resource consumption on a per-session basis. Many have found that their servers are able to service more connections by replacing OpenSSL with wolfSSL. Our engineers have

I was wondering if there was a %{char} that would give me the windows version or something equivalent so that Windows XP specific "stuff" doesn't get stuck with Windows 2000 "stuff". Thanks for the help. --Kaleb PS: Please CC me as I'm not on the list.

Hi Kaleb, Thanks, this refers to 3.11.x On Mon, Jul 3, 2017 at 4:16 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > On 07/03/2017 06:29 AM, Kaleb S. KEITHLEY wrote: > >> On 07/03/2017 04:34 AM, Atin Mukherjee wrote: >> >>> >>> On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: >>> >>> Hello Atin,

On 07/03/2017 06:29 AM, Kaleb S. KEITHLEY wrote: > On 07/03/2017 04:34 AM, Atin Mukherjee wrote: >> >> On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: >> >> Hello Atin, >> >> I've gotten around to this and was able to get upgrade done using >> 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't

Hi Darren, Tucker, and openSSH, wolfSSL is a dual licenced software. We have a Commercial option and a GPLv2 option. We provide support to both code sources and are an active part of the open source community. You can freely download our code from our website or visit our development branch on github. https://github.com/wolfSSL/wolfssl. https://wolfssl.com/wolfSSL/download/downloadForm.php

Thanks Kaleb, indeed, starting ganesha without HA works, but it's certainly not desirable, and everything is back to manual operations like in the old days. Do you have any time estimate for storhaug to be ready? Maybe it's worth to mention this in the documentation of 3.12 as well, otherwise other people will have the same problems. Cheers, ??? Alessandro Il 12/09/17 14:48,

On 08/17/2016 09:56 AM, Kaleb S. KEITHLEY wrote: > I propose to present on one or more of the following topics: > > * NFS-Ganesha Architecture, Roadmap, and Status,Jiffin Thotton copresenter. > * Architecture of the High Availability Solution for Ganesha and Samba > - detailed walk through and demo of current implementation > - difference between the current and storhaug

On 07/03/2017 04:34 AM, Atin Mukherjee wrote: > > On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: > > Hello Atin, > > I've gotten around to this and was able to get upgrade done using > 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't working well. > > On 3.11 though I notice that gluster/nfs is really

On Mon, 4 Jan 2016, Peter Stuge wrote: > Hi Kaleb, > > Kaleb Himes wrote: > > OpenSSH port Location: https://github.com/kaleb-himes/openssh-portable.git > > I'm afraid this repository is too messy to be useful. :\ > > You need to use the features offered by git to preserve commit ids if > anyone else besides yourself is going to be able to work with this, >

Thanks Kaleb, I presumed as much. I did previously try with 3.10 but ended up running into issues with pacemaker. I guess same question applied, can you point to any guides to a full setup of Ganesha on 3.10? Thanks From: Kaleb S. KEITHLEY <kkeithle at redhat.com> To: Jonathan Archer <jf_archer at yahoo.com>; "gluster-users at gluster.org" <gluster-users at

On 09/12/2017 11:35 AM, Alessandro De Salvo wrote: > Thanks Kaleb, > > indeed, starting ganesha without HA works, but it's certainly not > desirable, and everything is back to manual operations like in the old > days. > Do you have any time estimate for storhaug to be ready? It's been "soon" for a long time. It's still soon. > Maybe it's worth

To whom it may concern, I work for a company wolfSSL .Inc. Over the summer some of our engineers have worked to build openSSH with wolfSSL instead of openSSL as we were tired of constant security issues needing patched due to openSSL compilation. As a result of the efforts made we would like to submit a patch that offers users an alternate configure option when configuring openSSH

On 05/09/2018 09:02 AM, Roman Serbski wrote: > On Wed, May 9, 2018 at 1:22 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: >> >> That's certainly true. The issue hasn't been fixed in any version of >> gluster yet. >> >> You can help moving it along by voting +1 on >> https://review.gluster.org/19974 > > Will do -- thanks! >