search for: 9903

...9812 812 11494 16089 4595 148 4 98.31000 9812 814 4722 5657 935 149 4 98.31000 9812 815 3086 9563 6477 150 4 98.31000 9812 816 2493 3190 697 151 4 98.31000 9812 822 27540 31907 4367 152 4 98.31000 9812 825 1649 2255 606 153 5 97.90333 9903 4 3963 4094 131 154 5 97.90333 9903 5 2743 3002 259 155 5 97.90333 9903 6 4584 5495 911 156 5 97.90333 9903 7 3364 5210 1846 157 5 97.90333 9903 8 3476 4891 1415 158 5 97.90333 9903 9 2910 3256 346 159 5 97.90333 9903...

...via * (either CVS-HEAD-06/28/04-11:43:41 or CVS-HEAD-07/12/04-15:49:58) I didn't hear any ringing sound & get the following on the console: -- Called 5503 -- SIP/5503-f6b5 is ringing WARNING[-1323201616]: channel.c:1375 ast_indicate: Unable to handle indication 3 for 'SIP/10.10.2.250-9903' -- SIP/5503-f6b5 answered SIP/10.10.2.250-9903 Looking at channel.c, I can see that this means that 'condition' is neither of 'AST_CONTROL_PROGRESS' or 'AST_CONTROL_PROCEEDING'. Presumably it's 'AST_CONTROL_RINGING', so why is this not handled? (NB Calls...

...,0.22314355131421<tel:(435)%20513-1421>,0.22314355131421,-0.470003629245736,-0.470003629245736,-0.470003629245736,-0.470003629245736,-0.470003629245736,-0.470003629245736,-0.470003629245736,-0.470003629245736,-0.470003629245736,-0.470003629245736,-0.470003629245736,-0.470003629245736,-1.8562979903<tel:(856)%20297-9903>6563,-1.85629799036563,-1.85629799036563<tel:(979)%20903-6563>,-1.85629799036563,-1.85629799036563,-1.8562979903<tel:(856)%20297-9903>6563,-1.85629799036563,-1.85629799036563<tel:(979)%20903-6563>,-1.85629799036563,-1.85629799036563,-1.8562979903<tel:...

...netmask 255.255.255.0 broadcast 178.79.185.255 inet6 fe80::a8ad:d312:4ef4:7272 prefixlen 64 scopeid 0x20<link> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid 0x0<global> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) RX packets 9903 bytes 1088621 (1.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7786 bytes 1087223 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 That hardware address - the 18:8a:7e corresponds with what the IPv6 address is suppose to be. But tha...

....185.255 >> inet6 fe80::a8ad:d312:4ef4:7272 prefixlen 64 scopeid 0x20<link> >> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid >> 0x0<global> >> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) >> RX packets 9903 bytes 1088621 (1.0 MiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 7786 bytes 1087223 (1.0 MiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> That hardware address - the 18:8a:7e corresponds with what th...

...N=PosixAccount,CN=Schema,CN=Configuration,<RootDomainDN> cn: PosixGroup ldapDisplayName: posixGroup governsId: 1.3.6.1.1.1.2.2 objectClassCategory: 3 rdnAttId: cn subClassOf: top mayContain: cn, userPassword, unixUserPassword, description,gidNumber, memberUid schemaIdGuid:2a9350b8-062c-4ed0-9903-dde10d06deba defaultSecurityDescriptor: D:(A;;RPWPCRCCDCLCLORCWOWDSDDTSW;;;DA)(A;;RPWPCRCCDCLCLORCWOWDSDDTSW;;;SY)(A;;RPLCLORC;;;AU) defaultHidingValue: TRUE systemOnly: FALSE defaultObjectCategory: CN=PosixGroup,CN=Schema,CN=Configuration,<RootDomainDN> There are full details of what we h...

...er draws ships as white when direct3d is enabled 7268 Oni not opening after install 8185 can't login in Skype 3.1 on wine/kubuntu 7 8634 antialiasing disabled in gtasa menu 9555 Wine crash when I click help in Stata 10 9589 Static / Scratchy Sound with OSS in Call of Duty 9903 WinRAR with NXServer - black icons 10009 QIP: window z-order is still wrong 10268 Robot Wars: Arena of Destruction crashes while quitting (causing resolution to stay 640 x 480) 10322 Eve-online (video memory misaddressed?) 10700 Dragon Naturally Speaking 9 needs gdiplus.GdipDrawArcI,...

...sshd[1003]: [ID 800047 auth.error] error: PAM: User account has expired for user from pc00230.usr.domain.ru I found that getent passwd entries in Solaris and Linux are different solaris passwd entry: #getent passwd user user:x:103:103:user:/home/user:/bin/ksh ^^^ winbind entry: aduser:*:9903:2513::/export/home/aduser:/bin/sh ^^^ Help please with samba configuration. --

I''m a bit new on RoR so I might have missed something. I''ve just installed SaltedHashLogin and even though it works with no issues, it sends no emails. But I don''t get any errors at all! I''ve tried the method via the console: UserNotify.deliver_signup(User.new,"","") and I get the following: #<TMail::Mail

...fe80::a8ad:d312:4ef4:7272 prefixlen 64 scopeid 0x20<link> >>>> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid >>>> 0x0<global> >>>> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) >>>> RX packets 9903 bytes 1088621 (1.0 MiB) >>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>> TX packets 7786 bytes 1087223 (1.0 MiB) >>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>> >>>> That hardware address...

....0 broadcast 178.79.185.255 > inet6 fe80::a8ad:d312:4ef4:7272 prefixlen 64 scopeid 0x20<link> > inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid > 0x0<global> > ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) > RX packets 9903 bytes 1088621 (1.0 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 7786 bytes 1087223 (1.0 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > That hardware address - the 18:8a:7e corresponds with what the IPv6 address >...

...; inet6 fe80::a8ad:d312:4ef4:7272 prefixlen 64 scopeid 0x20<link> >>> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid >>> 0x0<global> >>> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) >>> RX packets 9903 bytes 1088621 (1.0 MiB) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 7786 bytes 1087223 (1.0 MiB) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> That hardware address - the 18:8a:7e corr...

...>>>> 0x20<link> >>>>>> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid >>>>>> 0x0<global> >>>>>> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) >>>>>> RX packets 9903 bytes 1088621 (1.0 MiB) >>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>> TX packets 7786 bytes 1087223 (1.0 MiB) >>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>>> >&g...

On 02/16/2017 12:54 AM, Tony Mountifield wrote: > In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581b5e at domblogger.net>, > Alice Wonder <alice at domblogger.net> wrote: >> https://forum.linode.com/viewtopic.php?f=19&t=14570&p=72785 >> >> I can not figure out what I need to do. >> >> Apparently according to linode support, the VM is trying to

Hello, I switched the first member server in production from 3.6 to 4.1. But since that, several times per day, smbd processes are crashing on that machine. Has anybody encountered this, too? [2013/11/05 04:14:43.532768, 0, pid=91892] ../source3/lib/popt_common.c:67(popt_s3_talloc_log_fn) talloc: access after free error - first free may be at ../source3/smbd/open.c:1529 [2013/11/05

...64 scopeid >>>>> 0x20<link> >>>>> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid >>>>> 0x0<global> >>>>> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) >>>>> RX packets 9903 bytes 1088621 (1.0 MiB) >>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>> TX packets 7786 bytes 1087223 (1.0 MiB) >>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>> >>>>> T...

...; >>>>>>>> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid >>>>>>>> 0x0<global> >>>>>>>> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) >>>>>>>> RX packets 9903 bytes 1088621 (1.0 MiB) >>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>>> TX packets 7786 bytes 1087223 (1.0 MiB) >>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >&gt...

...0x20<link> >>>>>>> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid >>>>>>> 0x0<global> >>>>>>> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) >>>>>>> RX packets 9903 bytes 1088621 (1.0 MiB) >>>>>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>>>>> TX packets 7786 bytes 1087223 (1.0 MiB) >>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>>&gt...

A few days ago, I tried to change the optimization flag from -O0 to -O2 to speed up the execution of the application on Ubuntu/ARM 14.04 32 bit. When I compiled the source code with -O2 flag instead of -O0 flag, I could not run the application normally by getting always the segmentation fault. Here is debugging information with GDB command in case of that. As you can see, we could not execute

OK, here is the large patchset that implements the virtio spec update that I sent earlier (the spec itself needs a minor update, will send that out too next week, but I think we are on the same page here already). It supercedes the PUBLISH_USED_IDX patches I sent out earlier. What will follow will be a patchset that actually includes 4 sets of patches. I note below their status. Please consider