Fmota Tech

In , Louis Hinman wrote:

You mean ‘/’ right? ‘/’ is the root of the unified UNIX/Linux directory tree for a single system. ‘/root’ is a directory (not usually a separate file system) that is normally used as the home directory of the “root” user.

Swap space isn’t part of the directory tree; it doesn’t have a pathname like this.

/home, /tmp, and /var/tmp (as well as any other world-writable directory) should be separate file systems. (They could reside on the same partition or even, as is in my case, on non-partitioned space.)

Other than that, I think the rest is really personal preference if you don’t want to share the file systems between multiple systems.

/usr, /usr/local, /opt, /var, /srv, /var/cache, /boot can each be justified as separate file systems, but I don’t think any are mandatory for your set-up.

I installed noip2 from apt-get before Apache. System responds that noip2 is functioning and I have NAT turned on in noip2.

Jacob Tennant – K8JWT

On Wed, Aug 4, 2010 at 11:44 AM, John Doe wrote:

In spite of the humour, the forum crowd is willing and probably able to help you solve your problem if you give us something to work with.

What error messages did you get?

Ron

On 04/08/2010 12:15 AM, Wayne Fay wrote:

Hi, While deploying the Struts Framework application on Jboss server, I am getting the error messages. Here with I am attaching errors.txt file for error messages.

Could any body guide/suggest to resolve my issue.

Thanks, http://old.nabble.com/file/p29303630/errors.txt errors.txt

Are you sure that’s the interface the connection is recieved on? If you actually listen on all interfaces on port 80, and your IP address changed, all your requests will hit the base server config instead of your name virtual host.

Apache HTTP Server (httpd) 2.2.16 Released

The Apache Software Foundation and the Apache HTTP Server Project are pleased to announce the release and immediate availability of version 2.2.16 of the Apache HTTP Server (“httpd”). This version of httpd is principally a security and bug fix release.

Notably, this release addresses CVE-2010-1452 (cve.mitre.org), a remote denial of service bug in mod_cache and mod_dav. This release further addresses the issue CVE-2010-2068 within mod_proxy_ajp, mod_proxy_http, mod_reqtimeout.

We consider this release to be the best version of httpd available, and encourage users of all prior versions to upgrade.

Apache HTTP Server 2.2.16 is available for download from:

http://httpd.apache.org/download.cgi

Please see the CHANGES_2.2 file, linked from the download page, for a full list of changes. A condensed list, CHANGES_2.2.16 provides the complete list of changes since 2.2.15. A summary of security vulnerabilities which were addressed in the previous 2.2.15 and earlier releases is available:

http://httpd.apache.org/security/vulnerabilities_22.html

Apache HTTP Server 2.2.16 is compatible with Apache Portable Runtime (APR) versions 1.3 and 1.4, APR-util library version 1.3, and APR-iconv library version 1.2. The most current releases should be used to address known security and platform bugs. At the time of this httpd release, the recommended APR releases are:

* Apache Portable Runtime (APR) library version 1.4.2 (bundled), or at minimum, version 1.3.12 * ARR-util library version 1.3.9 (bundled) * APR-iconv library version 1.2.1 (bundled only with win32-src.zip)

Older releases of these libraries have known vulnerabilities or other defects affecting httpd. For further information and downloads, visit:

http://apr.apache.org/

Apache HTTP Server 2.2 offers numerous enhancements, bug fixes, and performance enhancements over the 2.0 codebase. For an overview of new features introduced since 2.0 please see:

http://httpd.apache.org/docs/2.2/new_features_2_2.html

This release builds upon and extends the httpd 2.0 API. Modules written for httpd 2.0 will need to be recompiled in order to run with httpd 2.2, and may require minimal source code changes.

When upgrading or installing this version of httpd, please bear in mind that if you intend to use httpd with one of the threaded MPMs (other than the Prefork MPM), you must ensure that any modules you will be using (and the libraries they depend on) are thread-safe.

Hi all!

Some time ago I have been using x11vnc and xvncviewer in Debian GNU/Linux Lenny without problems. But today, after connecting to the server, I noticed that after moving the mouse and release it, this is positioned immediately in the upper left corner without giving me time to operate properly with the mouse.

I was trying tightvncserver and it does not exhibit this problem, but the idea is to share a session and I have open.

In case it helps, I’m noticing in /var/log/Xorg.0.log that there is a line saying “SetGrabKeysState – enabled” after logon in the remote machine and the next two lines after logoff:

SetClientVersion: 0 9 SetGrabKeysState – disabled

Any idea what could be the problem?

Thanks in advance for your reply.

Regards, Daniel

On Tue, 13 Jul 2010 20:20:15 +0000, Liam O’Toole wrote:

Hmmm… I knew that. The problem is that my http_proxy points to my squid server.

Did you really mean http_proxy, not soap_use_proxy?

cheers

Hi All,

I’ve noticed that asynchronous signals such as SIGINT, SIGTERM etc are delivered to my process long after the signal is sent if the receiving process is handling lots of I/O. My process is a multi-threaded web server. It’s got one thread waiting on ‘select’ to accept incoming connections and a thread pool which reads the data with ‘recv’.

When I batter the web server with incoming traffic and I try to shutdown the server by sending a SIGINT or SIGTERM, I have observed that the web server finishes handling the incoming traffic before the kernel dispatches the signal to the process. It appears that the ‘select’ and ‘recv’ calls are getting highest priority with regard to scheduling.

I realize this test may appear unnatural and is perhaps unrealistic, but I would like to be able to shutdown my server gracefully within a reasonable amount of time, no matter what kind of load it is handling. Don’t want to have to wait several minutes for my signals to get handled under heavy load. Could someone please explain why signal delivery is slow under these conditions?

Thanks in advance,

Dallas

On 09/07/10 06:48, surreal wrote: If you’re not able to find one with Google, then the rest of us probably won’t, either. That kind of thing is usually well indexed. If you can’t find one for lenny, that may be because the difference from etch is minimal and will be easily managed by someone who runs mail servers.

You’re less likely to find one for postfix than for exim4, which is the default Debian mail server. As far as exim4 goes, the only configuration change I made was to switch to maildir storage rather than mbox. Installation of Courier POP3/IMAP then made the necessary links, and set up a certificate in case I wanted IMAPS.

With exim4, you don’t add users, the users of the operating system are automatically included. It’s quite a few years since I used postfix, so I don’t know for certain that’s the same, but I would guess so. Even Windows does it that way, though of course it requires additional licences for each user.