search for: gates

Hi! After more work on the oplock_break problem, I've found the following in my tcpdump-smb logging. It seems that when ost5 (pid=26339 in the logs that follow) requests access to the oplocked file comm.inf from ost6 (pid=5872) the oplock_break failes (this is NOT isolated to any one or two systems on our network, just using these two as an example, and the server reports no dropped packets

> I love this question, simply because it allows me to talk about one > of the neatest features I programmed into my system that barely > anyone knows exists. Plus it lines up pretty much exactly with what > you are trying to do. > > We have our gate control system tied into our Asterisk phone system > so it is possible to dial a code on the phone and open the entrance

Hi Kevin. Thank you very much for the hint! It worked very well! Your example ' exten => 1234,1,System(echo "This is a test" >> /var/log/asterisk/test.txt) ' executes when the SIP client (my softphone Jitsi) sends a SIP INVITE to asterisk. So, the softphone tries to establish a session with target 1234. Now, lets suppose my softphone rings and I answer a

I've been getting a lot of these recently in my samba-log ever since I downloaded the latest cvs SAMBA_2_0 branch code. Mar 6 18:13:06 gate smbd[11126]: cos5 (192.168.7.132) connect to service rsession as user rsession (uid=707, gid=100) (pid 11126) Mar 6 18:13:15 gate smbd[11126]: [2000/03/06 18:13:15, 0] lib/fault.c:fault_report(40) Mar 6 18:13:15 gate smbd[11126]:

Hi! Been having the same problem with oplocks for a while and have been trying to figure out what's going wrong. The FAQ says that we may have a networking (hardware?) problem, but according to the Linux box's ifconfig results, we have had no errors and no dropped packets on the internal network. I am able to reproduce the error pretty much at will on our network, and it is not isolated

Hello Guys, I got trouble to get vserver work as gate: GATE=XX.XX.XX.XX YY_PORT=YY echo "1" > /proc/sys/net/ipv4/ip_forward iptables -F -t nat iptables -t nat -A PREROUTING -p tcp -i venet0:0 --dport $YY_PORT \ -j DNAT --to-destination $GATE:$YY_PORT iptables -t nat -A POSTROUTING -p tcp --dport $YY_PORT \ -j MASQUERADE iptables -L -t nat Any suggestion? I got

This patchset is for more paravirtualization on ia64/pv_ops. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/pv_ops. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/xen domU. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/xen domU. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

Recently LLD made it to the front page of HN (yay!): https://news.ycombinator.com/item?id=13670458 This comment about the Solaris linker surprised me: https://news.ycombinator.com/item?id=13672364 """ > To me, the biggest advantage is cross compiling Not all system linkers have this problem. For example, Solaris ld(1) is perfectly capable of cross-linking any valid ELF file.

Has anyone found a good wayt o do a gate intercom using Asterisk? I am looking at a Xorcom PBX with programmable contact, so I have no issue with opening the gate, but the interface at the gate is a bit tricky. I thought about a weather proof housing containing a phone but it seems a bit tacky. I also looked at a handsfree erather proof phone, but at $600 it is a bit steep. Any solutions that

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 more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi

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 more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi

Hello, I have a litle strnge problem with 3.0.23d on a SuSE 10.2. In Messages, I have hundreds of Messages like: ========================= Mar 9 14:59:19 v-gate nmbd[3664]: [2010/03/09 14:59:19, 0] nmbd/nmbd_incomingrequests.c:process_name_refresh_request(172) Mar 9 14:59:19 v-gate nmbd[3664]: process_name_refresh_request: unicast name registration request received for name VXP<00>

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 more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)

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 more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)

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 more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)

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 more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)

...on on the GUI and the user will have just to touch it, and the door or gate will open. I mean, during an ongoing call, the callee will see a button in the interface of its SIP application. For example, we can use the lib of Linphone and implement a GUI over it, having a new button to open doors and gates. So, the callee will not have to remember about codes, because there will be a button in someplace to be touched. When the button be touched, during an ongoing call, the software (SIP client) will sends a request to Asterisk executes the "gate => 9,self/callee,System,<insert command her...