10:10 p.m.
rc.local is executed after the init scripts on boot - what is the
equivalent which would be executed before the scripts during the shutdown
phase?
Thank you.
g/
10:40 p.m.
On Tue, 2007-07-31 at 23:10 -0400, Mail List wrote:
rc.local is executed after the init scripts on boot - what is the
equivalent which would be executed before the scripts during the shutdown
phase?
You probably want to look at: /etc/rc.d/rc0.d/S00killall It references
something else that *can* exist near the end.
--
[tim@bigblack ~]$ uname -ipr
2.6.22.1-33.fc7 i686 i386
Using FC 4, 5, 6 & 7, plus CentOS 5. Today, it's FC7.
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
8:48 a.m.
Tim wrote:
On Tue, 2007-07-31 at 23:10 -0400, Mail List wrote:
> rc.local is executed after the init scripts on boot - what is
the
> equivalent which would be executed before the scripts during the shutdown
> phase?
You probably want to look at: /etc/rc.d/rc0.d/S00killall It references
something else that *can* exist near the end.
I'm interested in this,
as one of my laptops goes completely black when I re-boot it
(either by "shutdown -r now" or by clicking on the Log out icon).
This doesn't do any harm, as it re-boots normally,
and comes up with the usual BIOS screen.
It's just puzzling.
To add to the puzzle, I have two identical laptops (ThinkPad T23's)
and this only happens on one ...
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
11:07 a.m.
At 2:48 PM +0100 8/1/07, Timothy Murphy wrote:
Tim wrote:
> On Tue, 2007-07-31 at 23:10 -0400, Mail List wrote:
>> rc.local is executed after the init scripts on boot - what is the
>> equivalent which would be executed before the scripts during the shutdown
>> phase?
>
> You probably want to look at: /etc/rc.d/rc0.d/S00killall It references
> something else that *can* exist near the end.
I'm interested in this,
as one of my laptops goes completely black when I re-boot it
(either by "shutdown -r now" or by clicking on the Log out icon).
This doesn't do any harm, as it re-boots normally,
and comes up with the usual BIOS screen.
It's just puzzling.
Is this the intentional screen-blanking that can be overridden by moving
the mouse or pressing the "Any" key, and avoided by removing "quiet"
(IIRC)
from the kernel boot line?
To add to the puzzle, I have two identical laptops (ThinkPad
T23's)
and this only happens on one ...
Now you have something to check?
--
____________________________________________________________________
TonyN.:' <mailto:tonynelson@georgeanelson.com>
' <http://www.georgeanelson.com/>
11:57 a.m.
Mail List wrote on Wednesday 01 August 2007:
rc.local is executed after the init scripts on boot - what is the
equivalent which would be executed before the scripts during the
shutdown phase?
The file /etc/init.d/halt calls /sbin/halt.local if it exists. But it does
so rather late in the shutdown process - maybe too late for your needs...
--
bye,
Adalbert
Digital Manipulator exceeding velocity parameters
10:58 p.m.
On Wednesday 01 August 2007 12:57:33 pm Adalbert Prokop wrote:
The file /etc/init.d/halt calls /sbin/halt.local if it exists. But it does
so rather late in the shutdown process - maybe too late for your needs...
* Thank you very much - this may be just what I need *
For my needs this will be perfect - I have encrypted /home but I did not
have luck getting encrypted / like my ubuntu friends - so I need to
cryptographically clean /tmp and /var/tmp on shutdown on my laptop for
security purposes. I plan to use a script which uses shred and tmpwatch to
clear them out.
Thank you ... I will try this.
2:44 a.m.
Mail List wrote on Thursday 02 August 2007:
> The file /etc/init.d/halt calls /sbin/halt.local if it exists.
But it
> does so rather late in the shutdown process - maybe too late for your
> needs...
* Thank you very much - this may be just what I need *
For my needs this will be perfect - I have encrypted /home but I did
not have luck getting encrypted / like my ubuntu friends - so I need to
cryptographically clean /tmp and /var/tmp on shutdown on my laptop for
security purposes. I plan to use a script which uses shred and tmpwatch
to clear them out.
Hm... I suppose it *is* too late then. The halt service tries to unmount
all filesystem before halt.local is executed.
If your problem is only encrypted /tmp (and maybe swap?) then crypttab
might be just what you want. (man crypttab) Crypttab is evaluated at
startup by cryptsetup and allows you dynamically setup an ecrypted /tmp
and swap - and maybe /var/tmp.
You might find http://www.familie-prokop.de/cryptofs/index_en.html
helpful. If crypttab is not applicable for you, then you will find 2 shell
scripts (cryptoswap, cryptotmp) at the bottom of this page. They can act
as system services and mount/unmount encrypted partition on
startup/shutdown.
--
bye,
Adalbert
To live is always desirable. -- Eleen the Capellan, "Friday's Child",
stardate 3498.9
2:51 a.m.
I have not read all the postings coming up to this one.
BUT, you mention 2.6.22
The last kernel that I was able to get vmware working with was 2.6.20.
There may be a workaround for the later kernels somewhere, but if I were you,
I would go out and pull (yum) one of the 2.6.20 kernels and install it.
That will give you the kernel and the stuff that vmware-config.pl is
asking for.
--
Reg.Clemens
reg(a)dwf.com
12:01 p.m.
Mail List wrote:
For my needs this will be perfect - I have encrypted /home but I did
not have luck getting encrypted / like my ubuntu friends - so I need
to cryptographically clean /tmp and /var/tmp on shutdown on my
laptop for security purposes. I plan to use a script which uses
shred and tmpwatch to clear them out.
Couldn't you just setup encrypted mounts for /tmp and /var/tmp? Then
you wouldn't have to worry with wiping them.
(Ignore me if I'm missing the obvious, I haven't played with encrypted
file systems in Fedora recently.)
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When I think about all the crap I learned in high school ... it's a
wonder I can think at all.
-- Paul Simon
9:56 p.m.
On Thursday 02 August 2007 01:01:50 pm Todd Zullinger wrote:
Mail List wrote:
Couldn't you just setup encrypted mounts for /tmp and /var/tmp? Then
you wouldn't have to worry with wiping them.
Well the fedora tools are not quite mature enough to do encrypted root (see
some older posts of mine). Trouble with this is i'd need to make 2
additional partitions - then i could run into same troubles I had getting
encrypted / with those.
My strong pref is use encrypted / via /etc/crypttab .. i'm hopeful F8 will
work cleanly (mkinitrd seems to be the biggest problem).
However I liked your idea and implemented it separately - because of the
troubles using /etc/crypttab I actually do the encryption via a scrript
called in rc.local. I have encrypted swap and /opt (my /home is actually a
link to /opt/home).
I created 2 dirs on my encrypted /opt partition - the idea is once /opt is
available then i can bind mount those 2 directories over /tmp and /var/tmp.
This accomplishes what you suggested without having to make any new physical
partitions and deal with separately encrypting them and the troubles that may
ensue.
So I added to /etc/fstab 2 lines:
# Use encrytped tmp var/tmp
#
/opt/tmp /tmp ext3 bind,noauto
/opt/var_tmp /var/tmp ext3 bind,noauto
Then in the scrript which actually does the luks open and mounts it
into /opt I added these lines:
mount /tmp
mount /var/tmp
It all works well - thank you for great suggestion!
g/
10:41 p.m.
Mail List wrote:
On Thursday 02 August 2007 01:01:50 pm Todd Zullinger wrote:
> Mail List wrote:
>
> Couldn't you just setup encrypted mounts for /tmp and /var/tmp?
> Then you wouldn't have to worry with wiping them.
Well the fedora tools are not quite mature enough to do encrypted
root (see some older posts of mine).
Yes, I saw them and had hoped someone might be able to help out. I do
think it's possible, but I've not kept up with the tweaks needed to do
encrypted /.
It all works well - thank you for great suggestion!
Thanks for posting the info so others can build on it. :)
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Procrastination is the art of keeping up with yesterday.
-- Don Marquis
12:39 p.m.
Mail List wrote:
On Wednesday 01 August 2007 12:57:33 pm Adalbert Prokop wrote:
> The file /etc/init.d/halt calls /sbin/halt.local if it exists. But it does
> so rather late in the shutdown process - maybe too late for your needs...
>
* Thank you very much - this may be just what I need *
For my needs this will be perfect - I have encrypted /home but I did not
have luck getting encrypted / like my ubuntu friends - so I need to
cryptographically clean /tmp and /var/tmp on shutdown on my laptop for
security purposes. I plan to use a script which uses shred and tmpwatch to
clear them out.
Thank you ... I will try this.
Make sure your /tmp isn't journaled or shred won't really work well.
From man shred
CAUTION: Note that shred relies on a very important assumption: that
the file system overwrites data in place. This is the traditional way
to do things, but many modern file system designs do not satisfy this
assumption. The following are examples of file systems on which shred
is not effective, or is not guaranteed to be effective in all file sys-
tem modes:
* log-structured or journaled file systems, such as those supplied with
AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.)
* file systems that write redundant data and carry on even if some
writes
fail, such as RAID-based file systems
* file systems that make snapshots, such as Network Appliance’s NFS
server
* file systems that cache in temporary locations, such as NFS
version 3 clients
* compressed file systems
In the case of ext3 file systems, the above disclaimer applies (and
shred is thus of limited effectiveness) only in data=journal mode,
which journals file data in addition to just metadata. In both the
data=ordered (default) and data=writeback modes, shred works as usual.
Ext3 journaling modes can be changed by adding the data=something
option to the mount options for a particular file system in the
/etc/fstab file, as documented in the mount man page (man mount).
--
Due to the move to Exchange Server,
anything that is a priority, please phone.
Robin Laing
1:35 p.m.
Somebody in the thread at some point said:
> laptop for security purposes. I plan to use a script which uses
shred
> and tmpwatch to clear them out.
>
> Thank you ... I will try this.
>
Make sure your /tmp isn't journaled or shred won't really work well.
ext4 is to have a cool feature I read some time ago, it can be asked to
crap on the sectors that contained a deleted file AND crap over the
metadata. I don't know if it takes care of the journal or not. It
takes care of overwriting the unlinked sectors lazily over the next
little while after the delete IIRC.
-Andy
6137
days inactive
6139
days old
12 comments
9 participants
participants (9)
-
Adalbert Prokop -
Andy Green -
clemens＠dwf.com -
Genes MailLists -
Robin Laing -
Tim -
Timothy Murphy -
Todd Zullinger -
Tony Nelson