[quote user="pauluskc"]the question remains if there were any signs around saying no parking. [/quote]
Nah; in British law the line in all important - if there are signs (only when there is single - not double yellow lines) they only apply to the area of road covered by the lines. I get this
several times a year, as I live near a big park which is used for a lot of celebrations (Diwali soon, followed by fireworks night), each time they try and make the road no parking.
But they can't place the cones if a car is already there.
BTW The word is "tyre" in English (being the language spoken by the English people). In the American dialect it may be spelt "tire" but we will teach you lot to spell one of these days.
dave1
@dave1
Best posts made by dave1
Latest posts made by dave1
-
RE: That's not a parking spot - really!
-
RE: I love mondays
Now that's scary... As you're obviously talking about a Unixlike server you should expect only to reboot on patching the kernel (or libc/glibc) - I once had an uptime on a Linux box of about 1200 days!
In terms of the space emails - what's wrong with just having boundary alerting? Panic the guy when he comes back - create a load of large files and then delete them (copy the kernel about 5000 times). -
RE: Don't use SSH
[quote user="coryking"]Was putty around in 1999? Before PuTTY there wasn't any good windows SSH client besides SecureCRT.[/quote]
Feh, in 1999 Windows boxen were only used for email and word processing. Unix workstations were used to do all that Unix admin stuff, the Windows boxen weren't stable enough to actually do any real work on...
I remember the bad old days (around 1994) when my Windows box was a 286, running Windows 3.11. One had no choice but to use the Unix workstation.
(I used mine all the way up 'til I stop being a Unix admin in around 2002, and then somebody else nicked it.) -
RE: Don't use SSH
[quote user="Alexis de Torquemada"][quote user="dave"]ssh can do that. ssh makes an encrypted tunnel (using symmetric encryption), authenticates, then changes to asymmetric encryption to do the rest.[/quote] It's exactly vice versa. Handshake using asymmetric cryptography, then encryption using a symmetric algorithm and a randomly generated session key.[/quote]
That's what I meant - I always get those two the wrong way around - just call it early senility.
[quote user="Alexis de Torquemada"][quote user="dave"] You can switch this to not encrypt. The advantage is speed, as you only need to encrypt on connection. If you're transferring gigabyte files around this is much more preferable.[/quote] But only if the file is already protected via some other means or its contents are not sensitive to either sniffing or data injection. If anyone is willing to do this, both the server and the client have to be configured to permit the NULL cipher, the default is (unsurprisingly) to prohibit use of the NULL cipher. (Also called eNULL where e stands for encryption, to distinguish from aNULL which applies to authentication.)[/quote]
Depends where you are - if you're on the internal LAN, then encryption of data flow generally tends to be one of those things that isn't essential, but encryption of credentials is more important (or just use keys to get round it).
Strangely enough, when we tested using different cyphers - blowfish beat the pants off even an unencrypted connection!