小弟在Linux 7.3下<em>安装</em>oracle 8.0.5时<em>提示</em>以下错误，result :relinking error. The executables for Oracle8 enterprise (RDBMS) were not made succesfully. please check the lgo file (/u01/app/oracle/product/8.0.5/orainst/install.log) and repeat the installation procedure for oracle8 Enterprise (RDBMS).请哪位大虾来帮帮我解决此问题啊，小弟将不尽感谢！！rn
最近又发生一个奇怪现象，使用loadlibrary()函数有时候会<em>hang</em>住不动。rnrn情况是这样的，我们公司写的软件，集成到AutoCAD上使用。 以前一直都运行挺好的，最近客户反映：在AutoCAD 2011, Windows 7环境下，会不定时地发生<em>hang</em>住的情况，使AutoCAD无法再继续使用。检查Task Manager,是我们的一个dxf2vec.exe一直在运行。rnrn我debug后发现，dxf2vec.exe在执行loadlibrary()时<em>hang</em>住了。rn像这样在特定环境：autocad2011 + windows 7中不定时发生的问题，请问如何解决？请高手给点建议，郁闷两天了。rn
<em>安装</em>delphi8.net时出现的<em>提示</em>请各位帮忙！！！！rnsetup has created a new file based upon the drivers you have selected for installationrndo you want to overwrite the existing copy of file with this one?rn
Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 2 bytes) in D:\APMServ5.2.6\www\htdocs\shopnc\core\framework\function\core.php on line 1366rnrn这段代码说明了啥，冒视内存有问题。不知为啥内存有问题呢
Spam, DDoS and phishing are common problems on the Internet nowadays. In the past, attackers tended to use centralized high bandwidth connections to accomplish their tasks. Now that home users have high bandwidth internet connections, attackers have started infecting and using these home computers instead to for their attacks. Attacking from distributed locations, attackers are harder to catch or stop and often have more bandwidth to abuse. New methods are required to detect the forming of these widespread networks of infected hosts, especially now that it seems attackers have discovered the peer-to-peer (P2P) technology.
checking for GL... configure: error: Package requirements (glproto >= 1.4.9 gl >= 7.1.0) were not met:rnrnRequested 'glproto >= 1.4.9' but version of GLProto is 1.4.8rnNo package 'gl' foundrnrnConsider adjusting the PKG_CONFIG_PATH environment variable if yourninstalled software in a non-standard prefix.rnrnAlternatively, you may set the environment variables GL_CFLAGSrnand GL_LIBS to avoid the need to call pkg-config.rnSee the pkg-config man page for more details.rnrnrn这是我在./configure时出的错，好像是在说要glproto 1.4.9 和gl 7.1.0 这两个包，第一个我已经安过了，第二个在网上找了半天没有找到，哪位大哥能给小弟指条明路，我已经从上午一直弄到现在了。
Given very few images containing a common object of interest under severe variations in appearance, we detect the common object and provide a compact visual representation of that object, depicted by a binary sketch.
Background and How Sessions Are Implemented rnrnASP.NET provides a framework for storing data that is specific to an individual user with the Session object. A page can add information to the Session object, and any other page can then retrieve the information for the same user. In order to preserve server memory, ASP.NET implements a rolling timeout mechanism which discards the session information for a user if no request is seen within the timeout period (default 20 minutes which is reset with each request). rnrnIt is often useful in an ASP.NET site to know for a particular request if the user’s session information is still intact (that a timeout has not occurred). One common need is to be able to inform the user why they lost their session information, by redirecting to a page that describes the timeout amount and how to avoid the problem in the future. Without this technique it is difficult to know if a session variable is not present whether it was never set properly or the user waited too long between requests. Many ASP.NET developers just reference session variables without first ensuring they are actually present. This causes the infamous "Object reference not set" exception, which can be very difficult to trace back to the specific cause. Code that checks for null session values is useful, but does not help the developer understand if it was never set properly or if the user just lost her session. This technique can help to clearly identify that the user waited to long between requests and the session storage information was removed.rnrnThis is not the same as using the Session_OnEnd event which can be used for cleanup, logging, or other purposes. It is also not for enforcing security on a web site. rnrnHow Sessions Are Implemented rnSince the HTTP protocol used by web browsers to request files from web servers is stateless, ASP.NET needs to determine which requests were from the same user. The primary mechanism utilizes a non-persistent cookie that is issued by the web server that contains a session id value. The id provided by this cookie is the key used to index into the session infrastructure to access the user's specific data. The session framework is implemented by the HTTP module System.Web.SessionState.SessionStateModule, which executes before the .aspx page events. The module uses the EnableSessionState attribute from the @Page directive to determine if it must retrieve the user’s session information (and whether it needs to write out c<em>hang</em>es when the request is complete). If the EnableSessionState attribute is true (which it is by default), the module retrieves all of the user’s session information and sets the Session property of the Page class to an instance of the HttpSessionState class. This article focuses on the cookie mechanism, although a cookie-less method of sessions is implemented in ASP.NET (the session id is embedded in the URL string). The Session information can be stored in-process (default, stores in web server memory), with a state service, or a SQL Server database. This article will focus on the in-process storage, but the technique applies to all three locations. rnrnExample User Session rnA user opens a browser instance and requests an ASP.NET page from a site. If the EnableSessionState attribute is true, the session module adds the ASP.NET_SessionId cookie to the response. On subsequent requests to the same web site, the browser supplies the ASP.NET_SessionId cookie which the server side module uses to access the proper user’s information. rn rnDetecting Timeouts rnrnrnrnThe ASP.NET HttpSessionState class provides a useful IsNewSession( ) method that returns true if a new session was created for this request. The key to <em>detecting</em> a session timeout is to also look for the ASP.NET_SessionId cookie in the request. If this is a new session but the cookie is present, this indicates a timeout situation. In order to implement this effectively for an entire web site, it is useful to utilize the “Base Page” concept described in a previous article.rnrnrnbasePageSessionExpire.csrnrnrn[code=C#] public class basePageSessionExpire : System.Web.UI.Pagern rn public basePageSessionExpire()rn rn rnrnrn override protected void OnInit(EventArgs e)rn rn base.OnInit(e);rnrnrn //It appears from testing that the Request and Response both share the rn // same cookie collection. If I set a cookie myself in the Reponse, it is rn // also immediately visible to the Request collection. This just means that rn // since the ASP.Net_SessionID is set in the Session HTTPModule (which rn // has already run), thatwe can't use our own code to see if the cookie was rn // actually sent by the agent with the request using the collection. Check if rn // the given page supports session or not (this tested as reliable indicator rn // if EnableSessionState is true), should not care about a page that does rn // not need sessionrn if (Context.Session != null)rn rn //Tested and the IsNewSession is more advanced then simply checking if rn // a cookie is present, it does take into account a session timeout, because rn // I tested a timeout and it did show as a new sessionrn if (Session.IsNewSession)rn rn // If it says it is a new session, but an existing cookie exists, then it must rn // have timed out (can't use the cookie collection because even on first rn // request it already contains the cookie (request and responsern // seem to share the collection)rn string szCookieHeader = Request.Headers["Cookie"];rn if ((null != szCookieHeader) && (szCookieHeader.IndexOf("ASP.NET_SessionId") >= 0))rn rn Response.Redirect("sessionTimeout.htm");rn rn rn rn rn[/code]sessionTimeout.htmrnrnThis can be any page on the site, example just redirects to this page so just show a simple "A timeout has occurred" message for this article.rnrnEach other page on the site just needs to derive from this new base page instead of the default System.Web.UI.Page, so just c<em>hang</em>e the line in the code behind class from ": System.Web.UI.Page" to ": basePageSessionExpire". Each page should also set the EnableSessionState variable as appropriate:rnrnfalse - page request does not access any session information (the base page uses this to know that it does not need to check for timeout on this request since it does not require session information) rnReadOnly - page request uses session information but does not modify it rntrue - page request reads and updates session informationrnConclusionrnIt is often useful to know for a given request whether the user’s session information is still present. The technique demonstrated is a straightforward implementation that can be easily applied to an entire web site that uses cookie based ASP.NET Session objects. rn rn