Tag Info

Hot answers tagged

3

easier than fdisk for your purpose is lsblk: $ lsblk --nodeps NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk sdb 8:16 0 298.1G 0 disk sr0 11:0 1 12M 0 rom or if you just want the drives: $ lsblk --nodeps -n -o name sda sdb sr0


3

Pulling out the foo.bar.baz.code.provider.com part can be done fairly easily in a couple of ways. For example: datacenter="$(echo "$HOSTNAME" | rev | cut -d. -f3 | rev)" If your data center names don't match a simple pattern like that, you could use a case statement, and match based on full shell patterns: case "$HOSTNAME" in *phx.provider.com) ...


3

You have to check your /etc/pam.d/passwd file if it includes /etc/pam.d/password-auth or /etc/pam.d/system-auth and to make required changed in file which is included. In short: An application that uses PAM can have a configuration file bearing its name in /etc/pam.d/. If a file exists, the rules in that file are processed whenever the application calls a ...


2

There are options you can use when you call fetchmail that will make it print out logs and debug information. Here's from the man page: For troubleshooting, tracing and debugging, you need to increase fetch- mail's verbosity to actually see what happens. To do that, please run both of the two following commands, adding all of the options you'd ...


2

You could do something like this, based on @derobert's answer: #!/usr/bin/env bash primary="/test01/primary" # copy primary_partition into this folder secondary="/test02/secondary" # copy secondary_partition into this folder holder_location_phx=("holdermachine.phx.host.com") # we might have more machines in future ...


1

In the simplest scenario, the so-called DDX (Device Dependent X) part of the X server will identify your video driver and use ioctl calls to initialize it, configure the video adapter and (usually) get the framebuffer address. The framebuffer will then be used for rendering. Here is a much more detailed description of the process. Things will get more ...


1

Unfortunately, there is no argument or option of chage that will apply all the changes made inside the login.defs fille to all the users. You will have to manually edit user by user with this little snippet that you provided on the question comments: # chage -m 1 -M 30 -W 14 some_existing_account This could be a real pain when you have a multiserver ...


1

Try this: blkid | awk -F":" '{print $1}'



Only top voted, non community-wiki answers of a minimum length are eligible