comp.security.ssh Google Group

PuTTY suppress pop-ups.

2010-01-04T21:46:52Z

I'm running putty on a Server 2003 box. Every now and then putty
loses the connection and creates a pop-up to notify me.
Problem is I need the session putty is providing to run 24/7. I'm
using Firedaemon to monitor things and keep putty running but while
that pop-up is there, Firedaemon thinks everything is fine.

Re: Copied files take up more space than originals

2009-12-31T15:38:12Z

Thank you Casper.
I was not aware of that. It seems it is also possible to copy using
tar on the same machine
Dave

Re: Can one configure sshd_config to allow only sshfs?

2009-12-28T04:17:38Z

I'm not sure about sshfs, but you can set a user's shell to be scponly
([link]) and they
won't get an interactive shell; only sftp.

Re: Copied files take up more space than originals

2009-12-24T16:26:43Z

Can ZFS really be used to mirror where the receiving end is mounted for
regular use or is this more like the tar method of tunneling the data
into a pipie just using data at a different layer of the stack.

Re: Copied files take up more space than originals

2009-12-24T11:10:50Z

cpio?
cpio -pmvd < list-of-files
across the network, use cpio -o | cpio -i
Casper

Re: Copied files take up more space than originals

2009-12-24T09:53:37Z

The intermediate file can be a pipe :
tar zcf - <dir> | ssh <user>@<target> "cd <destdir> && tar zxf -"

Re: Copied files take up more space than originals

2009-12-24T06:59:02Z

Your cluster size (minimum unit of allocation) is larger at the destination
than at the source.

Re: Copied files take up more space than originals

2009-12-24T06:02:38Z

Because there is a _huge_ deployed codebase out there, there is a
published API which would need significant revision, and making any
backwards incompatible changes to that API is hideously dangerous.
It's also impossible for the client to know, in advance, if the server
does or not support symlinks correctly, and vice versa. The risk is

Re: Copied files take up more space than originals

2009-12-24T05:25:09Z

["Followup-To:" header set to comp.security.ssh.]
So use rsync.

Re: Copied files take up more space than originals

2009-12-24T03:51:31Z

If you are using Solaris 10, use zfs pools and send/receive data.

Re: Copied files take up more space than originals

2009-12-24T02:00:34Z

Semi-related to this, I do need to find a way of copying files and
preserving links, like the '-a' option does on GNU 'cp'. I think
creating a tar archive and then extracting it might be one way, but
I'd like to avoid the need to create an intermediate file if
possible.
Dave
(PS, I am the original poster, also known as f...@coo.com depending on

Re: Copied files take up more space than originals

2009-12-23T18:11:52Z

The default behaviour does nothing at all. You must specify various
options in order to run rsync. The usual one is -a (for archive) and -v
( for verbose if you want to see which files are being transfered). As
he says, -H if you want hard links handled properly. There are many
options so skimming the man page is a good idea.

Re: Copied files take up more space than originals

2009-12-23T17:44:22Z

Dave wrote:
No. Why should the manufacturers of horse drawn carriages install all
of the safety features needed for the carriage to operate on an
Interstate highway? If you want to travel on an Interstate highway get
and use a car or truck not a carriage.
As discussed already tar and rsync are there for this use.

Re: Copied files take up more space than originals

2009-12-23T15:21:21Z

I would definitely use the tar solution or the rsync solution. Since
it's a relatively small amount of data 'tar' may be easiest.
I live for rsync these days too. I'm not sure rsync comes with
Solaris 10 by default. I've added it via Blastwave or OpenCSW, but
SunFreeware tools is good for that too.

Re: Copied files take up more space than originals

2009-12-23T14:43:34Z

Only if you specify -H as that is not default behavior.