similar to: What in samba 4.1 prevents a '/' share?

All, I've run samba in standalone mode since the 2.0.7 days and have been though a few breakages due to version updates along the way. It seems we have hit one again in the 4.4 to 4.5 update. Specifically, the update was samba-4.4.5 => samba-4.5.0 There were no changes made to smb.conf, but the following attempted mount failed using: mount.cifs //phoinix/samba /mnt/phx -o

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

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

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

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:

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

Jerry, Jeremy, et. al. Last night's upgrade from cifs-mount-3.2.0-24.1.121 to cifs-mount-3.2.0-24.1.122 on a openSuSE 10.3 x86_64 machine broke mount -t cifs. Now attempting to mount shares results in the following: 11:10 alchemy/home/david/bin] # mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass parsing options:

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]

Now hold on there... you said the problem started when you updated kernels - not when you changed the config file - did you change the config file or was it wrong before and the old kernel accepted it anyway? ted On 12/17/2013 10:08 AM, David C. Rankin wrote: > On 12/17/2013 10:43 AM, David C. Rankin wrote: >> Huh? Why the : in Servname? So I just hardwired it passing the port

On Dec 17, 2013, at 1:08 PM, David C. Rankin wrote: > 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

Sam, Danny, J., all I am working with the radeon and radeonhd drivers seeing if I can get them to work with compiz 0.8.2.1 on my radeon x1200 laptop. My xorg .conf is: Section "Device" BoardName "RV350 NP" # Driver "radeon" Driver "radeonhd" Identifier "Device[0]" VendorName "ATI" EndSection I have tried

Hello, I am an R newbie, trying to use lsoda to solve standard Lotka-Volterra competition equations. My question is: how do I pass a parameter that varies with time, like say, phix <- 0.7 + runif(tmax) in the example below. # defining function lotvol <- function(t,n,p){ x <- n[1]; y <- n[2] rx <- p["rx"]; ry <- p["ry"] Kx <-

On 12/14/2013 02:06 PM, David C. Rankin wrote: > Charles, > > Setting uid:gid to root:nut on /dev/bus/usb/004/002 seemed to be the issue. > The question now become how to automate this process so that the user isn't > required to manually hunt down the usb dev and change gid to the nut gid? So > far, either manually setting the gid or hand-rolling the udev files to do the

On Dec 14, 2013, at 4:23 PM, David C. Rankin wrote: > Do you know if the problem with upsdrvctl being able to probe/connect to the > usb devices is the result of some default permission change in Linux in general. > It seems to me that since nut used to work right out-of-the-box, then all/most > distros must have had the default permissions on usb nodes set to 0666, where >

On 12/14/2013 09:04 PM, Charles Lepple wrote: >> Is there someway nut can be modified to probe the 0664 permission usb >> devices >>> and then connect as root before dropping permissions back to the "nut" >>> gid? > Given that the udev method should still work (and seems to, for handcrafted > udev rules files), I would like to run that to ground first.

https://bugs.freedesktop.org/show_bug.cgi?id=78570 Priority: medium Bug ID: 78570 Assignee: nouveau at lists.freedesktop.org Summary: GT215: Freeze on X startup, 2014. QA Contact: xorg-team at lists.x.org Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: phix.nay at gmail.com

hi I'm puzzled as to the relation between the REML score computed by gam and the formula (4) on p.4 here: http://opus.bath.ac.uk/22707/1/Wood_JRSSB_2011_73_1_3.pdf I'm ok with this for poisson, or for quasipoisson when phi=1. However, when phi differs from 1, I'm stuck. #simulate some data library(mgcv) set.seed(1) x1<-runif(500) x2<-rnorm(500)