Displaying 16 results from an estimated 16 matches for "keld".
Did you mean:
held
2004 Jul 13
10
vulnerability with ssh-agent
...t is on would there be keys stored in the memory on the
machine logged in to (thus findable in /proc), or will ssh-agent there always
refer back to the machine logged in from?
Would there be a way for ssh-agent to have the keys stored in memory, so
that is not easily found in /proc?
Best regards
Keld Simonsen
2008 Jul 03
3
problem with lm and predict - no predictions made
...23 24
8.957402 9.019376 9.079867 9.139289 9.196752 9.250495 9.302067 9.351347
25 26 27 28
9.398927 9.446950 9.496094 9.545979
Why does predict not give me any predictions? The result of predict() is
same lenght (28) as the us and us.p variables.
best regards
keld
2008 Jul 04
3
problem with NA and if
...ue.
I then try to:
a = NA; if (a == NA) { a = 0}
just to try it out, but it says
Error in if (a == NA) { : missing value where TRUE/FALSE needed
What is wrong, and can I do it smarter? I looked at na.action but I
don't see how it affects addition of vectors, nor time series.
Best regards
keld
2006 Apr 16
2
e2fsck dies with signal 11
Hi
I got a strange error, happening on two of my ext3 partitions.
What can be wrong? And why does e2fsck error out, instead of displaying
an error message?
Best regards
keld
fsck /dev/hda6
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
Warning... fsck.ext3 for device /dev/hda6 exited with signal 11.
also From my dmesg:
<1>general protection fault: e7a8 [#3]
Modules linked in: i915 drm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device sn...
2006 Apr 21
2
EXT2-fs warning (device hda6): ext2_fill_super: mounting ext3 filesystem as ext2
I often get the message:
EXT2-fs warning (device hda6): ext2_fill_super: mounting ext3 filesystem as ext2
I have googled for a reason and a way to solve this -
but not found something I could use. Maybe somebody here konws
what to do?
best regards
keld
2006 Apr 21
1
problem with e2fsck not knowing xfs
Hi!
I had problem yesterday with e2fsck.
It reported a bad superblock.
I then tried to use one of the other superblocks.
To no avail.
Then later I remembered that I had switched the fs type to xfs.
Maybe e2fsck could recognize other common fs types,
and report this instead?
best regards
keld
2004 Jun 03
2
rsync preserving symlinks on mirror
...d they have the same problem.
What I do now, is to mount the raid directory on the mirror tree, but
that is ugly, as I cannot unmount it again, unless the raid fs is idle,
which seldom happens:-(
Any good suggestions? Have I overlooked a subtle option in rsync that
does this for me?
best regards
keld
2006 Jun 19
5
Limited write bandwidth from ext3
We are running a benchmark that does single threaded 512 KB writes to a
LUN on a CLARiiON storage array. The dual Xeon host (Dell 2650) with 4
GB of memory runs RHEL 4U3
We measured the write bandwidth for writes to the block device
corresponding to the lun (e.g. /dev/sdb), a file in an ext2 filesystem
and to a file in an ext3 file system.
Write b/w for 512 KB writes
Block device 312 MBps
Ext2
2006 Jul 26
4
data recovering in EXT3
Hello,
We have run and stopped by chance command "fsck -y" on one of our raid disks
(with ext3 file system). After that we have found that SOME files disappeared
(they are not seen in the directories where they have been before).
The data are extremely important and contain a lot of programs,
scripts for some data analysis and very hard to recover by hands.
I have run ''fsck
2006 Mar 28
0
Salvage or undelete files of damaged ext2/ext3 file systems
...may have been reused
unfortunately means that there may be errors in the salvaged files. So
check them afterwards.
The code is alpha and has only been tested on a Linux i386 system
Salvage is an addition to the debugfs program in the e2progs package by
Ted Ts'o.
Download: http://www.dkuug.dk/keld/e2fsprogs-1.38-ks1.tar.gz. Then
follow INSTALL instructions.
Author: Keld Simonsen, keld at dkuug.dk
2006 Sep 24
1
Retaining undelete data on ext3
Having just spent a day trying to recover a deleted ext3 file
for a friend, I'm wondering about this way of maintining
undelete information in ext3, like is done for ext2:
The last step in the deletion process would be to put back
the (previously zeroed) block pointers. Since it gets logged
to the journal, I _think_ that this should be safe. The worst
that would happen is that, if the plug
2006 Aug 29
2
Ext3 emergency recovery
I have a damaged Ext3 filesystem which fsck has not been able to
recover. If I try to mount it, I get a message like this in dmesg:
EXT3-fs error (device sda1): ext3_free_blocks_sb: bit already
cleared for block 2370866
If I try fsck on it, I get a series of messages like this:
Inode bitmap for group 0 is not in group. (block 0)
Relocate<y>?
Up to group 95. Some say
2008 Aug 30
1
logging rsync transfers in processable format
For my rsync daemon, I would like it to log in a format that I could run
some stats on, eg by webalizer that I use for http and ftp transfers.
Is that doable?
best regards
keld
2008 Aug 30
1
running rsync daemon as unpribileged
...ly the daemon runs root to get the 873 port opened.
And when transfers then run, they run as nobody.
I would like the rsync daemon to connect to 873 (as root)
then possibly do a chroot and then run always as something else
than root (maybe nobody).
It this advisable? Is it possible?
best regards
keld
2006 Nov 05
0
compressed read-only ext3 file system
...y 3 GB in under 2 minutes. The fs type I would like
to unpack is ext3 - but other fs types should be doable as well.
Then I would like to run the cd from the cdrom drive, so some kind of
live-cd running code should also be available.
Has this been done before? Is the idea feasible?
best regards
keld
2006 Apr 02
1
Zeroing freed blocks
A couple of years ago there was a discussion on lkml under the thread
'PATCH - ext2fs privacy (i.e. secure deletion) patch' about zapping
deleted data in the filesystem as a security mechanism. The discussion
wandered off into how 'chattr +s' could be implemented and whether
encrypting filesystems wouldn't be a better solution to the problem.
I've been maintaining a