Rebooting is for Windows • Hacker News Board

Re: Rebooting is for Windows

#41

Post by DerKommissar » Wed, Jul 28, 2010, 6:10 PM UTC

whacker wrote: post #30

cparedes wrote: post #28

Earlier quoted context omitted.

If your intention is to totally remove the space that's occupied by the log file, you'll probably want to pipe /dev/null into the file: cat /dev/null > /path/to/logfile

That does not do what you think it does. Your command will make /path/to/logfile fill up all available space on the disk. To truncate that file, which is probably what you wanted to do, you should `echo > /path/to/logfile`

His command does exactly what he says it does. Your command truncates the file and then writes a newline into it.

Re: Rebooting is for Windows

#42

Post by InclinedPlane » Wed, Jul 28, 2010, 6:52 PM UTC

Windows has greatly improved in this regard but it's still a huge pain point. I believe that the frequency of required reboots after patches is likely a leading cause for machines remaining unpatched.

Ultimately it comes down to lack of having "no reboots" as a clear goal. SQL Server has a pretty strong goal of being able to patch a running server without rebooting and they do a good job meeting that goal. For Windows OS it comes down to programmer laziness winning over in the absence of a directive to avoid reboots.

Re: Rebooting is for Windows

#43

Post by nailer » Thu, Jul 29, 2010, 2:16 PM UTC

slantyyz wrote: post #40

nailer wrote: post #38

Earlier quoted context omitted.

Yeah, but there's vendors who do half assed Windows versions too - Oracle comes to mind. Ultimately the VB/.net shops like BMC do shitty Unix versions, the big iron companies do shitty Windows versions.

You got that right. In the end, the target platforms are the vendors prerogative. Where you really run into problems is selling a weak Unix version into a Windows-hating shops. It ends up being more of a problem than if the vendor just told the customer "you're better off using Windows with our product".

Hate's a strong word, but yes, having a budget for such things in the past, a vendor coming in with an unpackaged app (or some horrible custom non RPM/deb packaging format), with no init scripts, no syslog support, and sales staff who don't understand the bog-standard RHEL or SLES platform to the point where you have to help them with their presentation, can and will guarantee no sale.

Re: Rebooting is for Windows

#44

Post by nailer » Thu, Jul 29, 2010, 2:20 PM UTC

slantyyz wrote: post #16

Pengwin wrote: post #12

Earlier quoted context omitted.

Exchange; that is quite a huge one for businesses where I am. Many people are just so used to outlook for email that when it comes for them to put in some kind of email management architecture they will always go exchange.

There are some non-Windows Exchange alternatives that would be transparent to Outlook users, but it's probably an uphill battle selling them to management.

Yes. You'll have better chance selling a new paradigm (cloud based, no clients to deploy, no individual mail server mattering) than a opened version of the old paradigm (which is still controlled by the proprietary vendor).