Does Furious Finish work with both hits of Cleaving Smash?

Cleaving Smash (from Weapon Trick – Two-Handed Weapon):

When you use Cleave, you can add the additional damage from Vital Strike to both your initial and your secondary attacks. If you also have the Greater Vital Strike feat, you can instead add the damage from Improved Vital Strike to both your initial and your secondary attacks.

Furious Finish:

While raging, when you use the Vital Strike feat, you can choose not to roll your damage dice and instead deal damage equal to the maximum roll possible on those damage dice. If you do, your rage immediately ends, and you are fatigued (even if you would not normally be).

Does Furious Finish apply to both hits of Cleaving Smash, or does rage suddenly end mid-swing?

Or are they not compatible at all since Cleaving Smash doesn’t directly state that you’re actually using the Vital Strike "feat", only that you’re getting all the benefits of it?

If I expanded all my movement, and Zephyr strike increase it by 30ft after my attack, can I finish my movement with the increased speed?

My character is a Ranger with the spell Zephyr Strike, which increase my speed by 30ft after the attack. If I used all my movement to reach the ennemy, can I use the increased 30ft to move away after my attack?

What are the repercussions of being able to finish a short rest in only 10 minutes instead of taking 1 hour?

Currently we are playing a horror adventure in D&D 5e. Due to circumstances (beings locked in a haunted house, rooms changing just when we close the doors, etc.), a 1-hour rest is hardly possible.

Our DM ruled that short rests can be as short as 10 minutes. The obvious result is that we can take it. What are other changes that we, both players and DM, should be aware of?

If it matters, party consists of Lore Bard, Vengeance Paladin, Chaos Sorcerer and Divination Wizard, all level 3.

Can Improved Cleaving Finish proc on itself?

Improved Cleaving Finish

If you make a melee attack, and your target drops to 0 or fewer hit points as a result of your attack, you can make another melee attack using your highest base attack bonus against another opponent within reach.

The way I understand it, Cleaving Finish is a passive proc. So, if I make a melee attack, kill Goblin A, I may immediately attack Goblin B. If this attack kills Goblin B, may I attack Goblin C? (D, E, F … )

(Note that Improved Cleaving Finish explicitly states that you can use Cleaving Finish any number of times per round)

Wait Command so Unrar will finish the first .rar then move to next

Below is the command user3140225 helped me out with and it works fine:

find /home/username/source/directory/ -type f -name "*.rar" -exec unrar e -o- {} /home/username/copy/extracted/to \; -delete && rm -r /home/username/source/directory 

Except I noticed it is uraring the .rar files from the separate folders (Folder1, 2) all at one time.

My structure is

  • SourceDirectory

    Folder1

    File .rar

    Folder2

    File .rar

I would like the one unrar to finish first before it goes on to the next one.

I am using cronjobs to run these commands. So if there is another way I would be grateful.

DP for Weighted Interval Scheduling: Can we sort start time in ascending order instead of the finish time?

Problem In the weighted interval scheduling problem, we want to find the maximum-weight subset of nonoverlapping jobs, given a set $ J$ of jobs that have weights associated with them. Job $ i \in J$ has a start time $ s_i$ , a finish time $ f_i$ , and a weight $ w_i > 0$ . We seek to find an optimal schedule — a subset $ \cal{O}$ of non-overlapping jobs in $ J$ with the maximum possible sum of weights.

Dynamic Programming Solution In almost all textbooks or materials I could get access to, a DP algorithm is given as follows: First all jobs are sorted in order of ascending finish time: $ f_1\le f_2 \le \dots \le f_n$ . Let $ OPT(i)$ be the maximum total weight of non-overlapping jobs in $ \{1,2, \cdots ,i\}$ , $ p_i$ be the largest index $ j < i$ such that job $ j$ and $ i$ are compatible. Then we see that $ $ OPT(i) = \max\{{w_i + OPT(p_i), OPT(i-1)}\}$ $

My question I think I could understand why this DP algorithm works. However I didn’t see the necessasity for the sorting step. What if we sort the finish time in ascending order instead? As far as I can see, it’s also correct.

MAAS using PXE won’t finish enlisting

Following the instructions in https://maas.io/install on a blade server I got stuck on the enlisting step. The PXE booting loads the image but after some reasonable time waiting nothing else happens. The blade is not shown in the Machines section. This is the PXE boot screen:

Intel(R) Boot Agent XE v2.3.58 Copyright (C) 1997-2015, Intel Corporation  CLIENT MAC ADDR: <BLADE_2_MAC_ADDRESS>  GUID: <GUID> CLIENT IP: 10.10.10.191  MASK: 255.255.255.0  DHCP IP: 10.10.10.1 GATEWAY IP: 10.10.10.254  PXELINUX 6.03 PXE 20171017 Copyright (C) 1994-2014 H. Peter Anvin et al Booting under MAAS direction... nomodeset ro root=squash:http://10.10.10.1:5248/images/ubuntu/amd64/ga-18.04/bio nic/daily/squashfs ip=::::maas-enlist:BOOTIF ip6=off overlayroot=tmpfs overlayro ot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc cloud-config-url=http ://10.10.10.1:5240/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed ap parmor=0 log_host=10.10.10.1 log_port=514 Loading ubuntu/amd64/ga-18.04/bionic/daily/boot-kernel... ok Loading ubuntu/amd64/ga-18.04/bionic/daily/boot-initrd...ok 

This is the server log when the blade PXE boots

myuser@blade-one:~$   tail -f /var/log/maas/rackd.log 2018-01-28 15:59:54 provisioningserver.rpc.clusterservice: [info] Fully connected to all 4 event-loops on all 1 region controllers (blade-one). 2018-01-28 15:59:55 provisioningserver.rpc.clusterservice: [info] Rack controller 'fddh8e' registered (via blade-one:pid=1748) with MAAS version 2.4.2-7034-g2f5deb8b8-0ubuntu1. 2018-01-28 15:59:55 provisioningserver.rpc.clusterservice: [info] Rack controller 'fddh8e' registered (via blade-one:pid=1750) with MAAS version 2.4.2-7034-g2f5deb8b8-0ubuntu1. 2018-01-28 15:59:55 provisioningserver.rpc.clusterservice: [info] Rack controller 'fddh8e' registered (via blade-one:pid=1751) with MAAS version 2.4.2-7034-g2f5deb8b8-0ubuntu1. 2018-01-28 15:59:55 provisioningserver.rpc.clusterservice: [info] Rack controller 'fddh8e' registered (via blade-one:pid=1749) with MAAS version 2.4.2-7034-g2f5deb8b8-0ubuntu1. 2018-01-28 15:59:55 provisioningserver.utils.services: [info] New interface monitoring state: {'enp5s0': {'neighbour': False, 'mdns': True}, 'enp6s0': {'neighbour': True, 'mdns': True}, 'ens1f0': {'neighbour': True, 'mdns': True}, 'ens1f1': {'neighbour': False, 'mdns': True}, 'virbr0': {'neighbour': True, 'mdns': True}} 2018-01-28 15:59:55 provisioningserver.utils.services: [info] Starting neighbour discovery for interfaces: {'ens1f0', 'virbr0', 'enp6s0'} 2018-01-28 15:59:55 provisioningserver.utils.services: [info] Neighbour observation process for ens1f0 started. 2018-01-28 15:59:55 provisioningserver.utils.services: [info] Neighbour observation process for virbr0 started. 2018-01-28 15:59:55 provisioningserver.utils.services: [info] Neighbour observation process for enp6s0 started. 2018-01-28 15:59:55 provisioningserver.utils.services: [info] mDNS observation process started. 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:grub-efi-signed:amd64:generic:uefi: to_add=['20190404.0'] to_remove=[] 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:grub-efi:arm64:generic:uefi: to_add=['20190404.0'] to_remove=[] 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:grub-ieee1275:ppc64el:generic:open-firmware: to_add=['20190506.0'] to_remove=[] 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:pxelinux:i386:generic:pxe: to_add=['20180807.0'] to_remove=[] 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-18.04-lowlatency:bionic: to_add=['20190814'] to_remove=[] 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:ga-18.04:bionic: to_add=['20190814'] to_remove=[] 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-edge:bionic: to_add=['20190814'] to_remove=[] 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-lowlatency-edge:bionic: to_add=['20190814'] to_remove=[] 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04-lowlatency:bionic: to_add=['20190814'] to_remove=[] 2018-01-28 15:59:55 sstreams: [info] maas:v2:download/maas:boot:ubuntu:amd64:hwe-18.04:bionic: to_add=['20190814'] to_remove=[] 2018-01-28 15:59:56 provisioningserver.utils.services: [info] observe-arp[ens1f0]: tcpdump: listening on ens1f0, link-type EN10MB (Ethernet), capture size 64 bytes 2018-01-28 15:59:56 provisioningserver.utils.services: [info] observe-arp[virbr0]: tcpdump: listening on virbr0, link-type EN10MB (Ethernet), capture size 64 bytes 2019-08-21 11:39:16 provisioningserver.utils.services: [info] observe-arp[enp6s0]: tcpdump: listening on enp6s0, link-type EN10MB (Ethernet), capture size 64 bytes 2019-08-21 11:39:19 provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: ens1f0, enp6s0, virbr0. 2019-08-21 11:39:39 provisioningserver.dhcp.detect: [info] External DHCP server(s) discovered on interface 'enp6s0': <OFFICE_DHCP_SERVER_IP> 2019-08-21 11:39:49 provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete. 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.0 requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.0 requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] ldlinux.c32 requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/40a55f1c-cea7-e511-bb26-020ba5d5cb1c requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/<BLADE_2_MAC_ADDRESS_WITH_DASHES> requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/0A0A0ABF requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/0A0A0AB requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/0A0A0A requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/0A0A0 requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/0A0A requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/0A0 requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/0A requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/0 requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] pxelinux.cfg/default requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:39 provisioningserver.rackdservices.tftp: [info] ubuntu/amd64/ga-18.04/bionic/daily/boot-kernel requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:47:40 provisioningserver.rackdservices.tftp: [info] ubuntu/amd64/ga-18.04/bionic/daily/boot-initrd requested by <BLADE_2_MAC_ADDRESS> 2019-08-21 11:48:11 rackd: [info] 10.10.10.191 GET /images/ubuntu/amd64/ga-18.04/bionic/daily/squashfs HTTP/1.1 --> 200 OK (referrer: -; agent: Wget) 2019-08-21 11:49:09 provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: ens1f0, enp6s0, virbr0. 2019-08-21 11:49:29 provisioningserver.dhcp.detect: [info] External DHCP server(s) discovered on interface 'enp6s0': <OFFICE_DHCP_SERVER_IP> 

Blade 1, where MAAS is installed is Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-58-generic x86_64) and MAAS is 2.4.2-7034-g2f5deb8b8-0ubuntu1

I followed these steps for installation:

  • Installed the maas package with sudo apt install maas
  • Added the first admin user with sudo maas init (Didn’t add any ssh key)
  • Logged in to http://:5240/MAAS/ and left all with default values. On the keys step added an ssh key generated for the blade-one server
  • Under Subnets accessed the VLAN for the subnet where the other blades will PXE boot and did “Provide DHCP”
  • Configured Blade 2 to PXE boot and booted

Should I use wizards steps if the user won’t finish all the steps at the same day?

I’m currently designing a system and there is this specific functionality that the user has to complete a series of steps, but the last step won’t be completed at the same day (it has a specific day to be completed). These previous steps are more like of a preparation to the last step itself.

Is it okay to use a linear wizard and let the user complete the last step later by saving its state or should I make this last step as a standalone page?