Changes between Initial Version and Version 1 of Ticket #235, comment 1
- Timestamp:
- Jan 11, 2014, 11:58:30 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #235, comment 1
initial v1 1 1 One of the solutions to this problem is to use "dhcpstrt" w/o arguments in the b4smb.cmd Samba script which contains tasks performed before starting daemons. From my experience, "dhcpstrt" started w/o arguments just waits until the background task (started by its another invocation from "\MPTN\bin\setup.cmd" during boot) finishes its job. I'm attaching the diff here. 2 2 3 However, I have a concern if this solution is an universal one as I don't know what "dhcpstrt" will do if the network interfaces are configured manually. Perhaps the "inetwait" commands should be used in such cases but this needs to be checked. Perhaps, the best way is to analyze the contents of "\MPTN\bin\setup.cmd" in b4smb.cmd and take an appropriate action based on how the network interfaces are configured — through DHCP or manually.3 However, I have a concern if this solution is an universal one as I don't know what "dhcpstrt" will do if the network interfaces are configured manually. Perhaps the "inetwait" commands should be used in such cases but this needs to be checked. Perhaps, the best way to do this is to analyze the contents of "\MPTN\bin\setup.cmd" in b4smb.cmd and take an appropriate action based on how the network interfaces are configured — through DHCP or manually.