Pre-Release2 : filesystem issues possibly related to .autofs

[ghost]

Recursive directory listing with "ls -alR / " hangs on .autofs
It eventually times out (takes about 3 minutes) and continues.

Then gets hung on /net (another long hang). it eventually continues to the end.

The command returns a non-zero value (1).

I will post an about(1) from that machine shortly.

[ghost]

about(1) output from this machine  (Lenovo T530)
root@trident-8164:~ # about
Project Trident Information
--------------------------------------
OS Version: 18.11-PRERELEASE_2
Build Date: 2018.11.28-21.47.41
--------------------------------------
TrueOS Sources Used:
  Base Repository: https://github.com/trueos/trueos
  Base Commit Tag: d4817554001ef23200da49d28756e36f498c17cb
  Ports Repository: https://github.com/trueos/trueos-ports
  Ports Commit Tag: ce8771a042dad00e7bbe62ca5c710b5d63813f57
--------------------------------------
System Specs:
  Boot Method: UEFI
  Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
  Physical CPUs: 4
  Physical Memory: 15.78 GB
--------------------------------------
GPU Information:
  vgapci0@pci0:0:2:0:   class=0x030000 card=0x21f517aa chip=0x01668086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '3rd Gen Core processor Graphics Controller'
    class      = display
    subclass   = VGA
--------------------------------------
Network Device Information
  em0@pci0:0:25:0:      class=0x020000 card=0x21f317aa chip=0x15028086 rev=0x04 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82579LM Gigabit Network Connection (Lewisville)'
    class      = network
    subclass   = ethernet
  iwn0@pci0:3:0:0:      class=0x028000 card=0x13118086 chip=0x00858086 rev=0x34 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Centrino Advanced-N 6205 [Taylor Peak]'
    class      = network
root@trident-8164:~ # 

[ghost]

ok, maybe a false alarm here.

the automountd service was not started. trident devs should it be started at boot?

"service automountd start" fixed it.

i'm keeping this ticket open for now and will watch for any other unexpected issues.

--Jim B.

[beanpole135]

There you go!
Those services used to be getting auto-enabled by the TrueOS base packages, but apparently we need to manually ensure they get set now.
The way that file works is that those are the recommendations, so if we add/change a recommendation, it will apply to the system during the next upgrade. If you disable one of the recommended services after that first automatic application, then it will remain that way across updates *unless * the project changes the recommendation for that service some time in the future (at which point it will restart and change it back to the recommended state). This is all done on a per-service level as well, so as not to "disrupt" a user's service configuration unless absolutely necessary.