On Thu, 29 Nov 2012 09:19:08 -0700
Gary Aitken articulated:
> Any reasons why one should not clear /var/tmp via periodic.conf?
From "/etc/defaults/rc.conf"
clear_tmp_enable="NO" # Clear /tmp at startup.
clear_tmp_X="YES" # Clear and recreate X11-related
Any process that stores data there would be really surprised when you clear
it:)
PHP uses tmp to store sessions and that is a good example:)
tmp may be cleaned after server restart
On Thu, Nov 29, 2012 at 8:19 PM, Gary Aitken wrote:
> Any reasons why one should not clear /var/tmp
On Nov 29, 2012, at 5:19 PM, Gary Aitken wrote:
> Any reasons why one should not clear /var/tmp via periodic.conf?
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To un
On Thu, 29 Nov 2012 09:19:08 -0700
Gary Aitken wrote:
> Any reasons why one should not clear /var/tmp via periodic.conf?
There are lots of things put in /var/tmp that programs expect to be persistent.
___
freebsd-questions@freebsd.org mailing l
Any reasons why one should not clear /var/tmp via periodic.conf?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
connection to session: Failed
> > to execute dbus-launch to autolaunch D-Bus session)
> >
> > and wrong date on /var/tmp/orbit-mexas (my username)
> >
> > % ls -al /var/tmp/
> > total 28
> > drwxrwxrwt 7 root wheel 512 18 Feb 15:48 .
> > drwx
d to enable TCP/IP networking for ORBit, or you have stale NFS
> locks due to a system crash. See http://www.gnome.org/projects/gconf/ for
> information. (Details - 1: Failed to get connection to session: Failed to
> execute dbus-launch to autolaunch D-Bus session)
>
> and wrong date on
http://www.gnome.org/projects/gconf/ for
information. (Details - 1: Failed to get connection to session: Failed to
execute dbus-launch to autolaunch D-Bus session)
and wrong date on /var/tmp/orbit-mexas (my username)
% ls -al /var/tmp/
total 28
drwxrwxrwt 7 root wheel 512 18 Feb 15:48
for
> information. (Details - 1: Failed to get connection to session: Failed to
> connect to socket /var/tmp/dbus-9QmJ2ebH21: No such file or directory)
> GConf Error: Failed to contact configuration server; some possible causes are
> that you need to enable TCP/IP networking for ORB
e possible causes are
that you need to enable TCP/IP networking for ORBit, or you have stale NFS
locks due to a system crash. See http://www.gnome.org/projects/gconf/ for
information. (Details - 1: Failed to get connection to session: Failed to
connect to socket /var/tmp/dbus-9QmJ2ebH21: No su
installed
gnome and all other packages from packages-7-stable/Lastest on the
website, and it gives me the error from the subject line, 'Could not lock
the file "/var/tmp/gconf-test-locking-file-blah"'. It says that it's an
NFS locking error, but I'm not using NFS.
Do y
dick hoogendijk wrote:
I'd like some info on:
man 7 hier:
"/var/tmp tempory files that are kept between system reboots"
Can I safely delete this directory. Probabl not 'cause it's kept in
between, but how can I weed some files then in a safe manner? What can
and what
I'd like some info on:
man 7 hier:
"/var/tmp tempory files that are kept between system reboots"
Can I safely delete this directory. Probabl not 'cause it's kept in
between, but how can I weed some files then in a safe manner? What can
and what cannot be deleted and why
On Mon, 3 Nov 2003 21:34:05 - "David Jenkins" <[EMAIL PROTECTED]> probably wrote:
> >On Mon, 3 Nov 2003, David Jenkins wrote:
>
> >
> >I have also tried:
> >
> > # chflags noschg empty/
> > chflags: empty/: Operation not permitted
> > chflags: empty/: Operation not permitted
> >
> > # chmod -
"David Jenkins" <[EMAIL PROTECTED]> writes:
> >On Mon, 3 Nov 2003, David Jenkins wrote:
>
> >
> >I have also tried:
> >
> > # chflags noschg empty/
> > chflags: empty/: Operation not permitted
> > chflags: empty/: Operation not permitted
> >
> > # chmod -R 0700 empty/
> > chmod: empty/: Operation
>On Mon, 3 Nov 2003, David Jenkins wrote:
>
>I have also tried:
>
> # chflags noschg empty/
> chflags: empty/: Operation not permitted
> chflags: empty/: Operation not permitted
>
> # chmod -R 0700 empty/
> chmod: empty/: Operation not permitted
>
> Please could someone point me in the right direc
On Mon, 3 Nov 2003, David Jenkins wrote:
>
> I have also tried:
>
> # chflags noschg empty/
> chflags: empty/: Operation not permitted
> chflags: empty/: Operation not permitted
>
> # chmod -R 0700 empty/
> chmod: empty/: Operation not permitted
>
> Please could someone point me in the right direc
Hi,
I am new to FreeBSD and recently completed my first build/installworld.
Everything went fine, except after running mergemaster it seems I have a
directory which I am unable to delete - /var/tmp/temproot.
When I searched the mailing lists I found a thread relating to this
problem but it did
But rc.local runs at the end of the startup - if something has already
put files in /var/tmp, they're going to disappear
Can't you use /etc/fstab to create & mount a memory disk?
- Original Message -
From: <[EMAIL PROTECTED]>
Subject: Sanity and /var/tmp
> Th
;
> > Is it safe and sane in a RELENG_5_1 system to create and use
> > /var/ tmp via a script in /etc/rc.local:
> >
> > [no entry in FSTAB]
> > mdconfig -a -t swap -s ... -u 10
> > newfs -O2 /dev/md10
> > mount /md10 /var/tmp
> > chmod 1
On Sunday 19 October 2003 12:36 pm, I sent a message with a few ugly
typos.
It should have read:
> This may be an incredibly stupid question. Nevertheless I'm gonna
ask...
>
> Is it safe and sane in a RELENG_5_1 system to create and use
> /var/ tmp via a script
This may be an incredibly stupid. Nevertheless I'm gonna ask...
(1) Is it safe and sane in a RELENG_5_1 system to create and use /var/
tmp via a script in /etc/rc.local:
[no entry in FSTAB]
mdconfig -a -t swap -s ... -u 10
newfs -O2 /dev/md10
mount /md10 /va
Hi,
# umount /var
# mv /var /usr
# ln -s /usr/var /var
In /etc/fstab remove the line containing /var
Regards
SSR
From: Joseph Maxwell <[EMAIL PROTECTED]>
To: FreeBSD Users <[EMAIL PROTECTED]>
Subject: Repositioning /var | /tmp to avoid disk full condition
Date: Sat, 31 May 2003 11
On Sat, May 31, 2003 at 11:58:23AM -0700, Joseph Maxwell
<[EMAIL PROTECTED]> wrote:
> How can I restore the full functioning structural integrity as before,
> of course the contents of the /usr/var directory was wiped out somwhere
> along the way, sans log, sans mail, sans everything. Just want to
cd /var
tar cf - . | (cd /usr/var; tar xf - )
cd /
rm -rf /var
ln -s /usr/var /var
However the 'rm -rf /var' returned
rm: /var: Device busy
After trying all known tricks to me to remove /var, I concluded that
since it was mounted from the /etc/fstab I should dismount it a
On Sat, May 31, 2003 at 11:58:23AM -0700, Joseph Maxwell wrote:
> Hello,
> The 3rd edition of "The Complete FreeBSD" suggest repositioning the /var
> directory ( and even /tmp) to prevent filling up that partition. I
> ignored it and did just that today, filled it up. So I attempted the
> repositio
/var/run:
/var/rwho:
/var/smtpd:
/var/spool:
/var/tmp:
/var/webmin:
/var/yp:
How can I restore the full functioning structural integrity as before,
of course the contents of the /usr/var directory was wiped out somwhere
along the way, sans log, sans mail, sans ever
27 matches
Mail list logo
