Log file stays empty when version 1.0.0 fails to unlock because it failed to create mount point

[mhogomchungu]

Running in the foreground

[ink@localhost .bin]$ ./securefs.1.0.0  m  abc /des --log ffff
Enter password:
fuse: bad mount point `/des': No such file or directory
[ink@localhost .bin]$ echo $?
1
[ink@localhost .bin]$ 

Running in the background

[ink@localhost .bin]$ ./securefs.1.0.0  m -b abc /des --log ffff
Enter password:
[ink@localhost .bin]$ echo $?
0
[ink@localhost .bin]$ stat ffff
  File: ffff
  Size: 0               Blocks: 0          IO Block: 4096   regular empty file
Device: 807h/2055d      Inode: 19803879    Links: 1
Access: (0664/-rw-rw-r--)  Uid: (  500/     ink)   Gid: (  500/     ink)
Access: 2024-04-24 15:59:38.112437464 +0300
Modify: 2024-04-24 15:59:37.349428047 +0300
Change: 2024-04-24 15:59:37.349428047 +0300
 Birth: 2024-04-24 15:59:37.349428047 +0300
[ink@localhost .bin]$ 

Prior versions will also not write to the log file but will print an error and return none zero return code.

[netheril96]

OK, I'm going to make a change in a few days so that the original process will wait until the child has either mounted successfully or failed, and will exit with the right code. This should solve both this bug and #177