similar to: Nt read is changing update status in UNIX

hen files are read under NT they are updating the access details under AIX as if they have been updated. I only want the inodes updated if the files have been changed, is there a setting in samba to ensure this happens rather than a read being taken as an update

Running Samba 2.2.2, having troubles with preexec when it involves the path parameter: Log on to the samba server as kris, user "users". %U expands to kris, %G expands to users. [profile] path = /data/profile/%U preexec = /bin/mkdir -m 700 /data/profile/%U writable = yes create mode = 0600 directory mode = 0700 This fails to work, Samba reports that it could not

Hello, I have a RELENG_6/AMD64 with an AMD64X2 cpu, 1GB of memory, 512MB swap. I remarked that when I run 2 simulation program [1], sometimes, one of them run one or several of its threads [2] very slowly, but sometimes, it doesn't occur. I remarked that is doesn't depend on SMP/UP, ULE/4BSD, i386/AMD64. It seems to occur also with the kernel stress test under the same conditions (all

Windows 7 Pro x64 Eaton 3S550 (brand new, battery mfg 8/15/2012) NUT 2.6.5-3 ups.status: OL CHRG CHRG was present even though it has been plugged in a few days turned on and battery.charge was 100%. Log includes me running upsc and removing power long enough to see that battery.charge will decrease. This UPS doesn't have controlled outlets despite what the upsc output says. ---

On 12/06/2013 10:57 PM, Kris Jordan wrote: > [...] > (*) Some UPS's do provide extra options to determine when they will > restore power to load. That would be a nice feature. Anyway, it is a strange thing that I can set the waiting time for power to be restored if main power comes back before offdelay has elapsed, but the UPS ignores this setting if main power comes back after

On Dec 4, 2013, at 3:52 PM, Kris Jordan wrote: > Roger Price wrote, On 12/4/2013 12:35 PM: >> I would like nut to become more loquacious, and to log a much more complete report of its activity. At present nut reports that its components have started operation but does not automatically log their activity when UPS's switch between OB and OL. I believe that this under-reporting of

If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? NOTIFYFLAG ONLINE SYSLOG NOTIFYFLAG ONBATT SYSLOG NOTIFYFLAG LOWBATT SYSLOG NOTIFYFLAG FSD SYSLOG NOTIFYFLAG COMMOK SYSLOG NOTIFYFLAG COMMBAD SYSLOG NOTIFYFLAG SHUTDOWN SYSLOG NOTIFYFLAG REPLBATT SYSLOG NOTIFYFLAG NOCOMM SYSLOG NOTIFYFLAG NOPARENT SYSLOG The 'wall'

Angel Tsankov wrote, On 12/24/2013 1:22 AM: > On 12/06/2013 10:57 PM, Kris Jordan wrote: > > [...] >> (*) Some UPS's do provide extra options to determine when they will >> restore power to load. > > That would be a nice feature. > > Anyway, it is a strange thing that I can set the waiting time for > power to be restored if main power comes back before

Been looking around for this. When does Samba determine when to check for changes to the smb.conf file? Is there a certain amount of seconds set? - Kris Jordan -

Charles Lepple wrote, On 7/31/2013 6:04 AM: > On Jul 30, 2013, at 1:36 PM, Kris Jordan wrote: > >> upsd removes its pid files when it's stopped, upsmon does not. > Hmm, interesting observation. Offhand, I think both should remove the PID files, but the way that upsmon drops root privileges might make this difficult. Makes sense. The manual says, --with-pidpath=PATH Changes the

Centos5 NUT 2.6.5, compiled from source I was reminded by a previous thread about a message I get when starting NUT... Starting upsd: fopen /var/run/nut/upsd.pid: No such file or directory Starting upsmon: kill: No such process upsd removes its pid files when it's stopped, upsmon does not. If I remove upsmon's manually after stopping it, I get a different message for it when I start

Hi, I have two types of UPS devices and one of them (APC) gave me a false "low battery" alert. I can't reproduce the problem... Also, there was nothing apparently wrong with the UPS at the time of the false alert. All I could do was grab the driver values within a minute after the "low battery" notification. These are the values: battery.runtime.low : 120

Nut for Windows 2.6.3-3 + Eaton/PW 5110 (103004256-5591). I had to manually install libusb driver and I'm using bcmxcp_usb. upsd.exe is reporting to me "Out of memory". It will run, but once anything connects to the daemon, it dies with that message. I don't have much experience with NUT yet so I'm not sure what the next course of action is. I do have NUT for Windows

Luke-Jr wrote, On 9/18/2013 1:02 PM: > I wanted to suggest some rating for functionality. I got the UPS available > that seemed to have the best possible rating from NUT's list (Eaton Powerware > UPS 1500), and found out it doesn't support telling me battery level or > runtime! :/ I'm avoiding Eaton/Powerware because the lack of usbhid support, the bcmxcp driver

Hi Kris, On 09/21/2013 05:11 PM, Kris Jordan wrote: > John Morris wrote, On 9/21/2013 11:28 AM: >> The most distressing problem is the UPS stays OB after removing and >> reapplying utility power. When power is removed, the UPS goes OB and >> upsmon detects the power failure no problem, reporting >> 's0-ups0 at localhost is on battery'. But when power is

I was wondering what you guys do about UPS shutdown on Windows systems? Apcupsd has the same issue, so I'm assuming it is the same with NUT. Windows just makes it hard/impossible to do. Do you find draining the batteries down so much cause issues for longevity? Regarding my Eaton 5110, I found that automatic driver setup works just fine on Windows XP but not at all on Windows 7 x64 (I

Roger Price wrote, On 12/4/2013 12:35 PM: > I would like nut to become more loquacious, and to log a much more > complete report of its activity. At present nut reports that its > components have started operation but does not automatically log their > activity when UPS's switch between OB and OL. I believe that this > under-reporting of important facts is too minimalist -

On Aug 1, 2013, at 1:34 AM, Kris Jordan wrote: > The kill error is coming from this line: > https://github.com/networkupstools/nut/blob/master/common/common.c#L263 > > Which is called from: > https://github.com/networkupstools/nut/blob/master/client/upsmon.c#L1930 > > In which case would you need to "see if this is going to work first"? Agreed, the first

On 12/25/2013 11:42 PM, Kris Jordan wrote: > Angel Tsankov wrote, On 12/25/2013 12:16 AM: >> >> What did you mean by "load.on.delay"? > > upscmd -l <ups> > > load.on.delay - Turn on the load with a delay (seconds) Alright, but... how does this command work? Once it has been executed, will the UPS wait the specified period before turning the load on

On Feb 25, 2014, at 1:13 AM, Kris Jordan wrote: > If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? > > NOTIFYFLAG ONLINE SYSLOG > NOTIFYFLAG ONBATT SYSLOG > NOTIFYFLAG LOWBATT SYSLOG > NOTIFYFLAG FSD SYSLOG > NOTIFYFLAG COMMOK SYSLOG > NOTIFYFLAG COMMBAD SYSLOG > NOTIFYFLAG SHUTDOWN SYSLOG > NOTIFYFLAG