similar to: upgrade 4.4 -> 4.5 broke standalone server smbmount of drives?

All, If the post "Samba 3.6 -> 4.1 change that prevent sharing / - mount error(13)" makes it to the list, I apologize, but it has been over a day and I have no indication that the post ever made it to the list. The issue is that in versions prior to 4.x, I was able to create a root share in samba, but now, something prevents it from being mounted. The relevant smb.conf is:

Charles, All, I just updated the kernel on my Arch box (the one we have been working on nut with on this list). Now upsd fails to start. (upsdrvctl is fine). I've posted working then -- Reboot -- the failing log information below. The 'Reboot' was for the kernel upgrade: Dec 14 14:02:00 phoinix systemd[1]: Starting Network UPS Tools - power devices information server... Dec 14

On 12/16/2013 09:23 PM, Charles Lepple wrote: > Not sure - I didn't write the getaddrinfo() code in upsd, but it seemed to > follow all of the recommendations on how to use that function. So if there is > a way to fix it in the NUT code, I am not aware of it (and would appreciate > any updates if that turns out to be the case). > > The odd part is that it looks like you went

All, Looking at logs for 4.1.3 on my standalone server (Archlinux w/systemd), I get an error launching samba with 'systemctl start samba.service' telling me I should start all individual daemons instead (nmbd/smbd/winbindd) of using samba.service: Jan 07 22:25:07 phoinix systemd[1]: Starting Samba AD Daemon... Jan 07 22:25:07 phoinix samba[29948]: [2014/01/07 22:25:07.734014, 0]

Samba Devs, Very strange error - smb fails to start on Archlinux after upgrade from 4.8.5 -> 4.9.2 on a simple standalone server. This server has run for years just fine through all upgrades, but on this one, smb cannot start: # sc -l --no-pager status smb ● smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) Active:

On 12/16/2013 08:01 PM, Charles Lepple wrote: > On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: > >> > Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for >> > ai_socktype > [...] >> > The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't see what >> > could have changed. How do I attempt to further

On Dec 16, 2013, at 10:11 PM, David C. Rankin wrote: > On 12/16/2013 08:01 PM, Charles Lepple wrote: >> On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: >> >>>> Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for >>>> ai_socktype >> [...] >>>> The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't

On 12/17/2013 10:43 AM, David C. Rankin wrote: > Huh? Why the : in Servname? So I just hardwired it passing the port "Servname" > as "3493" (could have just used "nut" from /etc/services): Sheepishly looking for a place to hide.... Yes there was a ':' there all right. Seems I was hit by a vi error: [12:04 phoinix:/etc/ups] # grep 3493 *.conf

In a mailbox that has ACL restrictions on both DELETE and EXPUNGE (i.e. no 'e' or 't' rights), I see the following: 3 UID STORE 3173 (UNCHANGEDSINCE 353) +FLAGS \deleted 3 OK Store completed. (UID 3173 is not flagged \deleted) [...] 6 UID EXPUNGE 1:* 6 OK Expunge completed. (At least 1 UID is flagged \deleted in mailbox) Shouldn't these commands be returning

On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: > Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for > ai_socktype [...] > The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't see what > could have changed. How do I attempt to further debug/fix this? getaddrinfo(3) is a libc function - is it possible that libc was updated as well? I am

I need to mount a share I don't have direct access to only to one subdirectory. I have no problems mounting other shares on the same windows server with the same permissions. I can mount the volume through gnome "Connect to Server...", but I need it on the filesystem. What is working: smbmount //server1/share1 /mnt -o -fstype=cifs -noperm,credentials=/etc/auto.smb.server1 What is

All, I have built and installed nut from git on Archlinux. It uses the usbhid driver. Beginning a couple of years ago, nut begin failing to run on Archlinux without 'tweaking' or 'fudging' the install. There are two primary problems: (1) upsdrvctl cannot be launched normally i.e. (/usr/sbin/upsdrvctl start) without failing to connect: Dec 14 02:24:39 phoinix systemd[1]:

On Mon, 29 Jan 2024 16:42:20 -0800 Peter Carlson via samba <samba at lists.samba.org> wrote: > > On 1/29/24 13:08, Rowland Penny via samba wrote: > > On Mon, 29 Jan 2024 12:51:37 -0800 > > Peter Carlson via samba<samba at lists.samba.org> wrote: > > > > > >> Just did a quick test, the big T comes after setting permissions in > >>

Hi, i have a rather weird and also problematic use case. My NAS provides permissions but I don't know how. The share is mounted using unix extensions and I am seeing user IDs. However my /local/ filesystem refuses me to allow to do anything unless I am root or set the noperms flag (ostensibly). This means that locally write access is denied but not remotely. The local user is UID 1000.

Hello, I have been doing a lot of research on this subject and I'm not finding a clear answer. My company currently makes a video capture and transcoding application that runs on a Linux server. The video application mounts shares from a second Linux storage server for various users at the same time. In other words, we have: A Linux Storage Server with many accounts (for example,

This patch exposes a generic interface which can be expanded in the future to implement USB for PVUSB, qemu, and stubdoms. It can also be extended to include other types of USB other than host USB (for example, tablets, mice, or keyboards). For each device removed or added, one of two protocols is available: * PVUSB * qemu (DEVICEMODEL) The caller can additionally specify "AUTO", in

Hallo, I've just tried kernel 3.4.6, self compiled, with the ".config" from kernel 3.3.7. Samba version 3.5.14 (slackware) When I run a script with (among many other lines) the command mount.cifs //$share/$src /path/to/$target \ -o noperm,sec=ntlmv2,$Loginparms (which runs without any problem under kernel 3.3.7) then I get an error message (some cifs problem), and the

openSUSE v13.1 linux 3.11.10-11-desktop x86_64 samba 4.1.6 I recently upgraded an openSUSE server from v12.3 to v13.1. In the older version there was no problem about mounting a remote volume offered by an ancient OS/2 system. Now there is. Trying to mount it by command line: root:/home/sma-user3x> mount /t2 Retrying with upper case share name mount error(6): No such device or address

Hi. I just got a new Windows 7 Home Edition computer and am unable to mount its shares on my Linux system. I'm running Fedora 11, samba 3.4.7 I have no trouble mounting shares from XP systems on the network using the mount command below. I can access the Windows 7 share with no problems using smbclient on Linux. The Windows 7 share is accessible from the XP systems. Here is the mount

I need a second pair of eyes here, please. I have a CentOS 6.6 server (let's call it 'S1") that has a Samba share on it that is currently working. We can mount that drive on our Windows work stations and transfer/delete from it just fine. It's setup as a "guest" config so no user specific passwords or any other restrictions like that. I'm trying to setup another