< ^ txt
Tue Jan 20 07:44:16 EST 2015
I'm up.
The sun is not.
Goals:
Work
- Finish IT plan for quarters two through four
Fleshed out a couple of projects, but not done.
- Start Scott on virtual app server install
Done. He's doing the Windows Server install now.
- Order Windows server 2012 R2 for Hazel Park backup server
Done.
...and for app server?
Holding off for a couple of days.
- Look at VPN's for remote workers
Started looking at npppd and L2TP
- Test EdgeRouter at property
Testing... Yes. A few firewall rules to work out, but this is good.
Home
- Study more C
Read a little more about pointers.
- Poke around at this fancontrol speed after wake issue
Sigh. I really need to learn more about systemd. Started some notes.
http://paulgorman.org/technical/linux-systemd.php
--- 605 --- bava ~ $ systemctl status fancontrol
● fancontrol.service - fan speed regulator
Loaded: loaded (/lib/systemd/system/fancontrol.service; enabled)
Active: active (running) since Tue 2015-01-20 19:55:57 EST; 1h 55min ago
Docs: man:fancontrol(8)
man:pwmconfig(8)
Process: 14307 ExecStartPre=/usr/sbin/fancontrol --check (code=exited, status=0/SUCCESS)
Main PID: 14386 (fancontrol)
CGroup: /system.slice/fancontrol.service
├─ 3394 sleep 10
└─14386 /bin/bash /usr/sbin/fancontrol
--- 609 --- bava ~ $ cat /lib/systemd/system/fancontrol.service
[Unit]
Description=fan speed regulator
# Run pwmconfig to create this file.
ConditionPathExists=/etc/fancontrol
After=lm-sensors.service
Documentation=man:fancontrol(8) man:pwmconfig(8)
[Service]
ExecStartPre=/usr/sbin/fancontrol --check
ExecStart=/usr/sbin/fancontrol
PIDFile=/var/run/fancontrol.pid
[Install]
WantedBy=multi-user.target
So, how is what gets run at boot different than what gets run at wake from sleep?
Questions:
- Where we specify multiple DNS servers for a system, how are they queried? Rotating, at random, as failovers?
http://superuser.com/questions/462926/how-do-preferred-and-alternate-or-multiple-dns-servers-work
http://www.unix.com/ip-networking/133552-howto-linux-multihomed-dns-client.html
If a nameserver times out, the next one specified in the list is queried.
This is the behavior of Linux; other operating systems may behave slightly differently.
`man resolv.conf` is informative. As is often the case, the OpenBSD man page is more informative than the linux man page.
Up to MAXNS (currently 3) name servers may be listed, one per
line. If there are multiple servers, the resolver library
queries them in the order listed. If no nameserver entries
are present, the default is to use the name server on the
local machine. (The algorithm used is to try a name server,
and if the query times out, try the next, until out of name
servers, then repeat trying all name servers until a maximum
number of retries are performed.)
< ^ txt