On 11/25/12 1:24 PM, Andrey Borzenkov wrote:
В Fri, 16 Nov 2012 17:37:27 +0100
Warpme пишет:
[Service]
ExecStart=/usr/local/bin/run-backup.sh
Type=forking
GuessMainPID=false
RemainAfterExit=no
Issue:
it works with:
ENV{ID_FS_LABEL_ENC}==".myth.backup", RUN+="/usr/bin/systemctl start
ext-usb
В Fri, 16 Nov 2012 17:37:27 +0100
Warpme пишет:
> [Service]
> ExecStart=/usr/local/bin/run-backup.sh
> Type=forking
> GuessMainPID=false
> RemainAfterExit=no
>
>
>
> Issue:
> it works with:
> ENV{ID_FS_LABEL_ENC}==".myth.backup", RUN+="/usr/bin/systemctl start
> ext-usb-backup.service"
>
Is
'Twas brillig, and Warpme at 18/11/12 18:38 did gyre and gimble:
> On 11/18/12 5:54 PM, Colin Guthrie wrote:
>
>>
>> Just as a general observation, I don't think you even need to delve into
>> udev rules to make all this work as systemd handles device mounts
>> internally.
>>
>>
>> You can simply
On 11/18/12 5:54 PM, Colin Guthrie wrote:
Just as a general observation, I don't think you even need to delve into
udev rules to make all this work as systemd handles device mounts
internally.
You can simply create a .mount unit for your drive such that when it is
inserted it is mounted autom
'Twas brillig, and Warpme at 16/11/12 16:37 did gyre and gimble:
> On 11/15/12 9:05 PM, Kay Sievers wrote:
>> You can use systemd to instantiate a service on device discovery (or
>> run a daemon that listens to events from udev on old init systems).
>> Check how bluetooth, cups printers, usbmux, ..
On 11/15/12 9:05 PM, Kay Sievers wrote:
You can use systemd to instantiate a service on device discovery (or
run a daemon that listens to events from udev on old init systems).
Check how bluetooth, cups printers, usbmux, ... is handled:
TAG+="systemd",
ENV{SYSTEMD_WANTS}="configure-printer@usb
On 11/15/12 9:05 PM, Kay Sievers wrote:
On Thu, Nov 15, 2012 at 7:40 PM, Warpme wrote:
Sometime ago upgraded my ArchLinux (kernel3.3.8) server to systemd195.
Today I discovered that my backup procedure fails. It was working OK with
previous systemd.
Forgive me if this forum is wrong place to as
On Thu, Nov 15, 2012 at 7:40 PM, Warpme wrote:
> Sometime ago upgraded my ArchLinux (kernel3.3.8) server to systemd195.
> Today I discovered that my backup procedure fails. It was working OK with
> previous systemd.
> Forgive me if this forum is wrong place to ask such questions, but as udev
> is
On Thu, Nov 15, 2012 at 07:40:19PM +0100, Warpme wrote:
> Hi *
>
> Sometime ago upgraded my ArchLinux (kernel3.3.8) server to systemd195.
> Today I discovered that my backup procedure fails. It was working OK
> with previous systemd.
> Forgive me if this forum is wrong place to ask such questions,
Hi *
Sometime ago upgraded my ArchLinux (kernel3.3.8) server to systemd195.
Today I discovered that my backup procedure fails. It was working OK
with previous systemd.
Forgive me if this forum is wrong place to ask such questions, but as
udev is now part of systemd - I decided to ask here...
I
10 matches
Mail list logo
