search for: fsr

...has vmware server running a BDC w2k3 r2 for fail-over and load balancing windows services. Here the file sharing is offered again by a samba server that shares archive folders. Now, how can i have the same shared folder on both file servers? I can adopt microsoft technology : use DFS filesystem and FSR replicas. Actually, i'm fallen in love with the DFS functionality that permit to uniform the namespace of file servers resource using only the name of the ad domain, but i hate the limits of FSR replicas. Hyp: - Think that i use DFS and setup that \mydomain\dfs\aaa refer to \firstserver\aaa and...

...mba 2.0.7 (build by the former administrator) and the workstations all ran windows 95. The samba-version is 2.2.3a with all security patches. We use the danish version of Windows 2000, and the error message when trying to log on is something like: "Systemet kunne ikke logge dig p? da dom?net FSR ikke er tilg?ngeligt" which means: "The system could not log you on since the FSR domain is not available" (FSR is the name of the domain). Samba runs as a PDC, but I've had workstations running windows 95 on the network and you couldn't log on to those either, so I guess th...

On Mon, Jun 15, 2015 at 12:43 AM, Nathan Anderson <nathana at fsr.com> wrote: > What you want is called SIP call forking, and unfortunately, last time I checked (before Asterisk 12 and the advent of PJSIP), Asterisk's SIP channel driver does not support it, and I would be shocked if Asterisk 12+ changes this situation. You can even see that people have...

...e to do is use a similar model to the modlme, but use (b/(c+(da^-z))) instead of log(da). Keeping d and habdiv as fixed effects and the sr-da relationship for each basin as a random effect. For the life of me I can not figure out the proper form of nlme. Any help would be greatly appreciated. Fsr<-function(da,b,c,z){b/(c+(da^-z} modnlme<-nlme(sr~d+habdiv+Fsr(da,b,c,z), fixed=, random=, start=)

...em together (this would match 23333 and 25555 and nothing else); exten => _2[35]RRR,1,DoStuff() exten => _2[35]RRR,n,AndMoreStuff() exten => _2[35]RRR,n,Dial(something) Am I missing something or does this really not exist? Thanks, -- Nathan Anderson First Step Internet, LLC nathana at fsr.com

...effectively and I can't seem to figure out how to make the output map larger. Do I need to change the device characteristics or is it a map.??? call. Here is the code: library(maps) library(geosphere) airports <- read.csv("airports.csv", header=TRUE) flights <- read.csv("FSRflights.csv", header=TRUE, as.is=TRUE) checkDateLine <- function(l){ n<-0 k<-length(l) k<-k-1 for (j in 1:k){ n[j] <- l[j+1] - l[j] } n <- abs(n) m<-max(n, rm.na=TRUE) ifelse(m > 30, TRUE, FALSE) } clean.Inter <- function(p1, p2, n, addStartEnd){...

On Mon, 2015-06-15 at 11:03 -0500, Matthew Jordan wrote: > On Mon, Jun 15, 2015 at 12:43 AM, Nathan Anderson <nathana at fsr.com> wrote: > > What you want is called SIP call forking, and unfortunately, last time I checked (before Asterisk 12 and the advent of PJSIP), Asterisk's SIP channel driver does not support it, and I would be shocked if Asterisk 12+ changes this situation. You can even see that people...

Hello group! I?m new to Asterisk but got one running finally :) Now I?m trying to solve following problem. I have company Automated Attendant and each employee have SIP phone at home, SIP phone in office, cell phone. I want all those 3 phones to be ?one?. So, if someone calls our company number and dials my extension - I?d like 3 phones to ring at the same time. What is this feature and where

...ensively studied, this is not the case for feature selection, despite of its importance. In a paper presented at SIGIR'07 [Tier1 in IR domain], the authors have highlighted the effectiveness of feature selection methods for ranking tasks.[link<http://research.microsoft.com/en-us/people/tyliu/fsr.pdf>] I believe that apart from the traditional/cliched IR features, we should*incorporate new features * to improve the performance of the LETOR module. *Using unlabeled data:* Over the last 3-4 years a lot of papers have identified the importance of using unlabeled data to assist the task at...

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on native

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on native

...struct nvkm_iccsense_sensor *sensor) +{ + struct nvkm_subdev *subdev = &iccsense->subdev; + /* configuration: + * 0x0007: 0x0007 shunt and bus continous + * 0x0078: 0x0078 128 samples shunt + * 0x0780: 0x0780 128 samples bus + * 0x1800: 0x0000 +-40 mV shunt range + * 0x2000: 0x0000 16V FSR + */ + u16 value = 0x07ff; + nvkm_debug(subdev, "config for sensor id %i: 0x%x\n", sensor->id, value); + nv_wr16i2cr(sensor->i2c, sensor->addr, 0x00, value); +} + +static void +nvkm_iccsense_ina3221_config(struct nvkm_iccsense *iccsense, + struct nvkm_iccsense_sens...

This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect call into in-place execution or direct call. The first patch imports helper functions which themselves doesn't interesting things. The second patch replaces the indirect function calls with a

This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect call into in-place execution or direct call. The first patch imports helper functions which themselves doesn't interesting things. The second patch replaces the indirect function calls with a

Hi! We're trying to figure out the best way to use samba4 in our environment and after testing back and forth we are now left with a question; why would we want to have several samba4 servers? The environment is one HQ with multiple branch offices where each branch office as a network connection to HQ with at least a 2Mbit DSL. The initial idea was to put a samba4 DC in every branch

OK, it's been a while since I drank from the pool of wisdom hear on the list. After cracking my head against the wall for a few days trying to figure this out, I have decided to swallow my pride and take the drink. So, on to my question: I have some agents/operators setup in sip.conf which point to a context where I have just about disabled outbound calls (only specific numbers can be