2012-07-18 21:07:51 +04:00
# pragma once
2010-01-23 03:52:57 +03:00
2010-02-03 15:03:47 +03:00
/***
This file is part of systemd .
Copyright 2010 Lennart Poettering
systemd is free software ; you can redistribute it and / or modify it
2012-04-12 02:20:58 +04:00
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation ; either version 2.1 of the License , or
2010-02-03 15:03:47 +03:00
( at your option ) any later version .
systemd is distributed in the hope that it will be useful , but
WITHOUT ANY WARRANTY ; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE . See the GNU
2012-04-12 02:20:58 +04:00
Lesser General Public License for more details .
2010-02-03 15:03:47 +03:00
2012-04-12 02:20:58 +04:00
You should have received a copy of the GNU Lesser General Public License
2010-02-03 15:03:47 +03:00
along with systemd ; If not , see < http : //www.gnu.org/licenses/>.
* * */
2010-01-23 03:52:57 +03:00
typedef struct Automount Automount ;
2010-01-26 23:39:06 +03:00
# include "unit.h"
2010-01-23 03:52:57 +03:00
2012-02-03 06:27:25 +04:00
typedef enum AutomountResult {
AUTOMOUNT_SUCCESS ,
AUTOMOUNT_FAILURE_RESOURCES ,
core: move enforcement of the start limit into per-unit-type code again
Let's move the enforcement of the per-unit start limit from unit.c into the
type-specific files again. For unit types that know a concept of "result" codes
this allows us to hook up the start limit condition to it with an explicit
result code. Also, this makes sure that the state checks in clal like
service_start() may be done before the start limit is checked, as the start
limit really should be checked last, right before everything has been verified
to be in order.
The generic start limit logic is left in unit.c, but the invocation of it is
moved into the per-type files, in the various xyz_start() functions, so that
they may place the check at the right location.
Note that this change drops the enforcement entirely from device, slice, target
and scope units, since these unit types generally may not fail activation, or
may only be activated a single time. This is also documented now.
Note that restores the "start-limit-hit" result code that existed before
6bf0f408e4833152197fb38fb10a9989c89f3a59 already in the service code. However,
it's not introduced for all units that have a result code concept.
Fixes #3166.
2016-05-02 14:01:26 +03:00
AUTOMOUNT_FAILURE_START_LIMIT_HIT ,
2016-05-02 17:51:45 +03:00
AUTOMOUNT_FAILURE_MOUNT_START_LIMIT_HIT ,
2012-02-03 06:27:25 +04:00
_AUTOMOUNT_RESULT_MAX ,
_AUTOMOUNT_RESULT_INVALID = - 1
} AutomountResult ;
2010-01-23 03:52:57 +03:00
struct Automount {
2012-01-15 15:04:08 +04:00
Unit meta ;
2010-01-23 03:52:57 +03:00
2010-04-21 05:27:44 +04:00
AutomountState state , deserialized_state ;
2010-01-23 03:52:57 +03:00
2010-04-17 01:24:39 +04:00
char * where ;
2015-04-14 23:01:48 +03:00
usec_t timeout_idle_usec ;
2010-04-17 01:24:39 +04:00
int pipe_fd ;
2013-11-20 00:12:59 +04:00
sd_event_source * pipe_event_source ;
2010-08-12 00:37:10 +04:00
mode_t directory_mode ;
2010-04-17 01:24:39 +04:00
dev_t dev_id ;
Set * tokens ;
2015-04-14 23:01:48 +03:00
Set * expire_tokens ;
sd_event_source * expire_event_source ;
2010-04-17 01:24:39 +04:00
2012-02-03 06:27:25 +04:00
AutomountResult result ;
2010-01-23 03:52:57 +03:00
} ;
2010-01-26 23:39:06 +03:00
extern const UnitVTable automount_vtable ;
2010-01-23 03:52:57 +03:00
2013-05-03 06:51:50 +04:00
const char * automount_result_to_string ( AutomountResult i ) _const_ ;
AutomountResult automount_result_from_string ( const char * s ) _pure_ ;