GNU ps supports BSD-style options, UNIX-style options, and GNU long options. Is using one of these types (in scripts and at the command line) preferred over the others?
I get the impression from the manpage that the functionality of the option styles does not overlap completely.
I'm using CentOS and Red Hat Enterprise Linux on a few machines without the GUI. How can I check if recently installed updates require a reboot? In Ubuntu, I'm used to checking if /var/run/reboot-required is present.
Is there a piece of equipment that connects to a wireless network and provides ethernet ports to clients?
I have an existing wireless network, and I would like to plug a bunch of machines into a single switch that uses the wireless network as an uplink.
Is this possible, or is this a bad idea? The bandwidth utilization through this link should be negligible.
I have a server running Postfix 2.6.5, and all of the local users have email accounts through the company ISP. These accounts have the same usernames as their usernames on the server.
I would like any locally sent email (i.e., sent to [email protected] or just joe) to be sent directly to the ISP accounts (i.e., [email protected]). I don't want the users to even have mailboxes on the server.
Using smtp_generic_maps looks close, but I think it requires a separate line for every user in the system. Do I need to put regexps in generic? Or is there an easier way to do this?
If I were to archive data on a hard drive, unplug it, and set it on a (not dusty, temperature-controlled) shelf somewhere, would that drive deteriorate much?
How does the data retention of an unplugged hard drive compare to tapes?
Using ps, I can see the size, the vsize (same as top's VIRT?), and the rss (same as top's RES?). (One more I see in top is SHR.)
Could someone summarize for me what these different fields mean?
Right now, a group of our employees is using Skype for group chats and conference calls. They're not using telephone numbers, just Skype user accounts.
I'd like to set up a server that will provide similar functionality that is only accessible inside the LAN.
What I'm not looking for is something to use with real telephones.
The main problem with Skype is that the Linux client is terrible and getting worse every year they don't update it. I also don't like the idea of our company data going through Skype servers (yes, I know it's encrypted).
SIP seems to be quite a pain, but there's also GnuGk and Jabber+Jingle.
Whatever it is, I'd like to also support Windows clients.
Is there anything out there that's open source and easy to administer?
Let's say I'm setting up a single machine server. Without knowing the specific components in it (and being able to look up their MTBFs), what are the typical relative failure rates of the hardware components in the server?
Equivalently, what are the rankings of the most often-replaced components across all the servers in corporate use?