<la:message key="labels.crawling_info_button_back"/>
                                    </button>
                                    <c:if test="${editable}">
                                        <button type="button" class="btn btn-danger" name="delete"
                                                data-toggle="modal" data-target="#confirmToDelete"

                                </c:if>
                                <div class="row">
                                    <c:if test="${editable}">
                                        <la:form action="/admin/joblog/">
                                            <div class="col-sm-12 center">

                                    <la:message key="labels.joblog_button_back"/>
                                </button>
                                <c:if test="${editable}">
                                    <button type="button" class="btn btn-danger" name="delete"
                                            data-toggle="modal" data-target="#confirmToDelete"

 * constructor’s flag handling, response creation and simple accessors.
 *
 * <p>All tests run in the same package as the class under test so that
 * package‑private members are visible if required.
 */
@ExtendWith(MockitoExtension.class)
class SmbComNTCreateAndXTest {
    @Mock
    Configuration mockConfig;
    @Mock
    ServerMessageBlock mockAndX;
    @Mock
    CIFSContext mockContext;

public class MyClass
{
   final Logger logger = LoggerFactory.getLogger( MyClass.class );
}
+-----+

* Logger Name

 Logger name is basically the classical fully qualified class name: it's not visible by default, but can be activated (see {{{/maven-logging.html}user documentation}}).

                                        <la:message key="labels.searchlog_configuration_button_back"/>
                                    </button>
                                    <c:if test="${editable}">
                                        <button type="button" class="btn btn-danger" name="delete"
                                                data-toggle="modal" data-target="#confirmToDelete"

                                </c:if>
                                <div class="row">
                                    <c:if test="${editable}">
                                        <la:form action="/admin/crawlinginfo/">
                                            <div class="col-sm-12 center">

                                        <la:message key="labels.crud_button_back"/>
                                    </button>
                                    <c:if test="${editable}">
                                        <button type="button" class="btn btn-danger" name="delete"
                                                data-toggle="modal" data-target="#confirmToDelete"

    }

    @Override
    protected Executor executor() {
      transitionStates.add(state());
      return directExecutor();
    }
  }

  // Functional tests using real thread. We only verify publicly visible state.
  // Interaction assertions are done by the single-threaded unit tests.

  private static class DefaultService extends AbstractIdleService {
    @Override
    protected void startUp() throws Exception {}

## Log Targets

MinIO supports currently two target types

- console
- http

### Logging Console Target

Console target is on always and cannot be disabled.

### Logging HTTP Target