Maybe there's indeed some problem with your kernel or device. I tried
the following rule on my machine:
/etc/udev/rules.d/usb.rules:SUBSYSTEM=="usb", RUN+="/usr/bin/bash -c
'echo $ACTION $DEVPATH >> /home/tom/test"
And here's the "test" log after I reboot and plug/unplug a usb thumb
drive (2-4):
a
To check my understanding of how per-connection socket activation
works, I've tried to make a very simple socket-activated service which
runs any input through md5sum, writes md5sum's output to the journal,
and then sleeps for one second. What I have works, but only
sometimes. Frequently, no md5s
Hi,
Ohne way is to use an More recent Kernel, with 3.16+ the Kernel defaults for
These values where changed to unlimeted
Regards Florian
Von meinem iPhone gesendet
> Am 26.08.2015 um 17:34 schrieb Chris Bell :
>
> Hello all,
>
> I'm attempting to run GitLab (with postgresql) on a CentOS 7 c
Hello all,
I'm attempting to run GitLab (with postgresql) on a CentOS 7 container
with systemd-nspawn. Postgre keeps failing, because it tries to allocate
more shared memory than the container seems to allow. I cannot use
sysctl to write the kernel.shmmax and kernel.shmall properties, since
/
On Wed, 26 Aug 2015 15:32:13 +0200 (CEST)
wrote:
> >They are not referring to your device, but the machine on which you
> >are
> running the rule.
> >In a terminal/console you run: udevadm monitor
> >The do the removal itself and see what 'udevadm monitor' says.
>
> this is the problem: the mach
>They are not referring to your device, but the machine on which you are
running the rule.
>In a terminal/console you run: udevadm monitor
>The do the removal itself and see what 'udevadm monitor' says.
this is the problem: the machine which are running the rule is a "specific
robotic device" wit
On Wed, 26 Aug 2015 14:43:35 +0200 (CEST)
wrote:
> >can you show how you confirmed your script receive the "add" event,
> >or how the script "catch" the event?
>
> Sure: basically I do "echo "USB_$ACTION" >> /tmp/jc.log".
> After plug/wait/unplugged/wait I only see lines "USB_add".
> See attache
>can you show how you confirmed your script receive the "add" event, or how the
>script
>"catch" the event?
Sure: basically I do "echo "USB_$ACTION" >> /tmp/jc.log".
After plug/wait/unplugged/wait I only see lines "USB_add".
See attached my .rules and .sh scripts.
>Can you paste run `udevadm mo
Hi
On Wed, Aug 26, 2015 at 1:04 AM, Thomas H.P. Andersen wrote:
> On Wed, Aug 26, 2015 at 12:40 AM, David Herrmann
> wrote:
>> Hi
>>
>> Trying to continue with our bi-weekly release schedule, we plan to
>> release version 225 tomorrow. Please give it a spin and make sure
>> there is no major br
Can you paste run `udevadm monitor`, plug in your cable/device, wait
for a second, unplug it, and paste the output? Or can you show how you
confirmed your script receive the "add" event, or how the script
"catch" the event?
On 26 August 2015 at 15:35, wrote:
>>> I am not sure about what you mean
>> I am not sure about what you mean here. Do you mean that you can't see
> any remove event with `udevadm monitor` when you unplug the "cable"?
yes, my script never receive the "remove" event (_but_ receive the "add" event).
>> Also do you really mean a "usb cable" without any device connected
11 matches
Mail list logo
