[MuzzleVelocity]

I assumed it was to run some commands when a USB device is connected, but what I found seems strange:

I added a command to echo a message to the serial console into this USB script. During bootup I saw my message flash five times, the first one well before the kernel even initialized the USB subsystem.

whats actually triggering this script to run?

(I'm running v3.0-r46885 on an EA8500, but I'm posting to the General Forum because I have no way of knowing if this behavior is specific to Qualcom hardware.)

Thanks.

[kernel-panic69]

Added in build 06-10-2020-r43381 (but not noted in build release threads?):

[MuzzleVelocity]

[kernel-panic69]

You could probably just post the actual details and discussion right here in this thread so we can actually see what is going on and if it's a bug or not that needs to be reported. Quite honestly, there is a lot of tickets that get opened on Trac that don't get any attention unless someone emails BrainSlayer about them more often than not and people don't seem to get this.

[MuzzleVelocity]

i attached a screenshot of what I put in the USB script, and also attached the dmesg kernel log.

Its executing the script around 15 seconds, before the usbcore even loads.

It then executes it twice right before sda1 actually gets mounted, and then twice more right after.

[kernel-panic69]

Have you tried echoing that to /proc/kmsg or other logging facility or using a different method to print to the log to see if it does the same thing?

https://unix.stackexchange.com/questions/585919/what-is-the-difference-between-proc-kmsg-and-dev-kmsg

https://stackoverflow.com/questions/28235333/what-is-the-difference-between-proc-kmsg-and-dmsg/28247699

https://unix.stackexchange.com/questions/503059/writing-to-dev-kmsg-randomly-shows-up-in-proc-kmsg-and-always-in-dmesg

https://unix.stackexchange.com/questions/205883/understand-logging-in-linux

[MuzzleVelocity]

I changed the USB Script to /proc/kmsg from /dev/kmsg, but then nothing showed up at all. (I then tried echoing to /proc/kmsg directly from the command line and got a "Write error: I/O error")

I did originally have the USB script echoing to /dev/console and watching the results in hyperterminal. There werent timestamps on everything like with dmesg, but I definitely saw 5 occurences, and they were spaced apart similarly to what is shown in the kernel log.

[SurprisedItWorks]

try the logger command. should be easy to google the man page. Or just try these by hand in the CLI and then look at the syslog:

echo 'This is a message' | logger -t 'the originator'

logger <<'EOF' -t 'the ultimate loginator!'
This is a multi-line
message that will likely
make an ugly log entry.
EOF

[MuzzleVelocity]

ok, I tried the logger command. Here is an excerpt from the syslog. It indicates the same behavior, being executed 5 times.

[egc]

I think this is to start a script from USB drive so let the script point to the log script on the USB drive and see if it is executed

Scripts/services are started multiple times that in itself does not necessarliy indicate a bug

[MuzzleVelocity]