search for: 19542

...Request from f8:ca:b8:06:7d:ed (oui Unknown), length 359 --- stot tcpdump uefi pxe boot --- As you can see, nothing happens, no ARP or anything else. But it will show up in dnsmasq-log while trying UEFI PXE Boot: --- start dnsmasq-dhcp-uefi-boot --- Feb 27 10:52:44 dhcpd.localdomain dnsmasq-dhcp[19542]: 3645383917 available DHCP range: 172.22.132.2 -- 172.22.137.254 Feb 27 10:52:44 dhcpd.localdomain dnsmasq-dhcp[19542]: 3645383917 available DHCP range: 172.22.21.2 -- 172.22.23.254 Feb 27 10:52:44 dhcpd.localdomain dnsmasq-dhcp[19542]: 3645383917 vendor class: PXEClient:Arch:00007:UNDI:003016 Feb...

...s correctly and the entry in the logfile is: Sep 24 07:01:20 garm sshd[6625]: Accepted password for japs from 192.38.97.131 port 2463 Next I have upgraded to openssh-3.7.1p2 and restarted SSHD. It does not accept the password any more and the entries in the logfile are: Sep 24 12:21:38 garm sshd[19542]: User japs not allowed because account is locked Sep 24 12:21:38 garm sshd[19542]: Failed none for illegal user japs from 130.225.127.34 port 50593 ssh2 Sep 24 12:21:41 garm sshd[19542]: Failed password for illegal user japs from 130.225.127.34 port 50593 ssh2 The /etc/sshd_config is the same in...

...ng [100 at default:1] NoOp("SIP/rf.com-b69da2f8", ""Inbound call for Eric!"") in new stack -- Executing [100 at default:2] Dial("SIP/rf.com-b69da2f8", "SIP/ exten1") in new stack == Using SIP RTP CoS mark 5 [2009-06-09 15:31:39.107] ERROR[19542]: chan_sip.c:4003 create_addr_from_peer: 'UDP' is not a valid transport for 'exten1'. we only use 'TLS'! ending call. Really destroying SIP dialog '03ad15856b352c3f2956812075bb7483 at 10.254.105.188 ' Method: INVITE [2009-06-09 15:31:39.107] WARNING[19542]: app_...

In crossbow, each mac_srs has a kernel thread called "mac_rx_srs_poll_ring" to poll the hardware and crossbow will wakeup this thread to poll packets from the hardware automatically. Does crossbow provide any method to disable the polling mechanism, for example disabling the this kernel thread? Thanks Zhihui -------------- next part -------------- An HTML attachment was scrubbed... URL:

...-O2 conftest.c >&5 >configure:19479: $? = 0 >configure:19482: test -s conftest.o >configure:19485: $? = 0 >configure:19496: result: yes >configure:19511: checking for uint64_t >configure:19536: gcc -c -g -O2 conftest.c >&5 >configure:19539: $? = 0 >configure:19542: test -s conftest.o >configure:19545: $? = 0 >configure:19556: result: yes > >All seems to be fine... > >/Henrik > >> >>Not sure if this will help, but something is terribly wrong, possibly with >>the definition of int64_t. Note that the message from the com...

...ould like to read that version, otherwise, the details are as follows: Dovecot 2.0.19 Postfix 2.9.6 Ubuntu 12.04 The actual error message I receive is --------------------------------------------------------------- postfix/pickup[16842]: 019023A06AB: uid=1000 from=<vagrant> postfix/cleanup[19542]: 019023A06AB: message-id= <20130620140358.019023A06AB at mail-server-berkshelf> postfix/qmgr[16843]: 019023A06AB: from=<vagrant at mail-server-berkshelf.localdomain>, size=382, nrcpt=1 (queue active) dovecot: lda: Debug: Loading modules from directory: /usr/lib/dovecot/modules dovecot:...

Hi, i am new to rails and trying to understand the migrate feature of rake whenever I call "rake migrate", i understand it call all the latest version of a given of given migrate files. Now when these files are executed, id the #down method called and then the #up ? or must i explicitly call the #down method from rake. If yes how do i do that from rake ? I experimented with rake

...t64_t configure:19476: gcc -c -g -O2 conftest.c >&5 configure:19479: $? = 0 configure:19482: test -s conftest.o configure:19485: $? = 0 configure:19496: result: yes configure:19511: checking for uint64_t configure:19536: gcc -c -g -O2 conftest.c >&5 configure:19539: $? = 0 configure:19542: test -s conftest.o configure:19545: $? = 0 configure:19556: result: yes All seems to be fine... /Henrik > >Not sure if this will help, but something is terribly wrong, possibly with >the definition of int64_t. Note that the message from the compiler is not >"can't find o...