Date: Thu, 10 Jul 2014 18:18:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 191781] [patch] multimedia/webcamd - much improved rc.d script Message-ID: <bug-191781-13-ingHFjtwvN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-191781-13@https.bugs.freebsd.org/bugzilla/> References: <bug-191781-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191781 --- Comment #9 from dreamcat4@gmail.com --- (In reply to Hans Petter Selasky from comment #8) > Hi, > > That sounds like a good idea. Maybe you can do the "usbconfig" only once, > and then pass it through a regular expression like "grep -iE -- xxx". You Yes. > should accept multiple matches. This makes a dependency for usbconfig, but I Probably OK because usbconfig is included in FreeBSD base. > think that is OK. Possibly this functionality could be integrated into > webcamd aswell, which might be more clean? Yes indeed. In fact all these function would be better inside webcamd (forking / spawning) as C code is faster and give better performance. I can make very easy in the rc.d script right now, which take just 1-2 days. Which can be done right away. Then later on, when you eventually can work on the C daemon, it can replace any stuff in rc.d script with C mechanism of daemon. But first it may help to decide beforehand possible interface for C daemon, when starting up multiple instances. For example if webcamd rc.d script wants to start on 2 identical device then we make some fixed delay of n seconds (normally 0,1, or 2 seconds) to avoid possible conflict of /dev/dvb node names being grabbed. Yet if the webcamd 'C' daemon had some good lock mechanism communicate with it's sister processes. It could reserve node names ahead of initialization, then 2 instances can be started simultaneously without such delay. And the 2nd instance can see the reserved /dev/ node names, and avoid them. This is important if the time taken to initialise the USB hardware device is not constant. It could be less than 1 second, or several seconds. > > What do you think? > > --HPS -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-191781-13-ingHFjtwvN>