And to add a few things:
Never, ever, ever, ever remove (rm -rf) /tmp. Ever. /tmp is not just
another directory. This is where daemon-session information can, and is
recorded, xwindows sockets and data is stored/etc. That's why redhat created
TMPwatch (check your cron directories) TMPwatch goes through and removes any
files not touched in X time. This prevents file buildup.
On /tmp itself, it has special attributes (Stickybits for 1) that
allow the system to store temporary values in it (values to inane or too
important, or too temporary to store in /var). You'll find these /tmp
attributes the same across all linux distros in fact.
So, to sum up, technically, via the 'LSB' and other entities, the
socket file for a given daemon should either go in /var or in the /log of a
given daemon's directory stucture.
However, in actual execution, /tmp is fine. Sure, it's not
completely and totally standards compliant, but it is not as if we're
storing logs and socket files in /etc.....
But, i agree with you and Tom, it's not the nicest way of handling
things, but it's really a pain to change.
ok. Back to work for me.
-jesse
-----Original Message-----
From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 11, 2001 10:14 AM
To: CF-Linux
Subject: RE: CF 4.5 webserver.log on Linux
Rob,
You have hit on two problems with the web server stub all tied to the same
issue: The stub has no configuration information on Unix.
We use hard coded path names (/tmp and /opt/coldfusion) to find the socket
and to write the stub log file.
The log file issue is a reasonable complaint, this is something that got
missed when the log directory feature was added.
I certainly wouldn't think that any system would run very well if
the entire /tmp directory was removed. I sometimes regret putting
the socket there (yes, it was me, way back in CF 3.1) and not in
the /opt/coldfusion directories, but at the time we did not have
any well known place to find things. We later made it a requirement
that /opt/coldfusion has to point to the install directory, wherever
that really lives, but by this time it was difficult to change the
location.
--
Tom Jordahl
MacroMedia Server Development
-----Original Message-----
From: Rob Patrick [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 08, 2001 5:46 PM
To: CF-Linux
Subject: CF 4.5 webserver.log on Linux
I've noticed that with Cold Fusion 4.5.1 SP2 Enterprise Edition on Linux
that if you go in to the Administrator area and change the log directory
(under logging | settings) that most of the log and PID files will reflect
the change, but the webserver.log file is still kept and updated in
/opt/coldfusion/log/.
Is there any workaround to get the webserver.log file pointed at a different
directory? I really hadn't planned on having growing files under /opt, and
prefer to use /var/log/cfusion for all CF logging purposes. Can we use a
symlink on this file? Maybe I ought to just symlink the log directory to
/var/log/cfusion...
Thanks,
-Rob Patrick
Also, just in case somebody in the future is searching the list archive, do
NOT remove the directory /tmp on a Unix system running Cold Fusion, as it
will cause cfexec to repeatedly crash in a terrible loop, as it uses
/tmp/cfserver for the cfserver and cfexec processes. Macromedia/Allaire
might want to put something under settings for this to be
changed...especially if it isn't already covered in the docs somewhere.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
