Thanks Jyri, All,
Creating a Lighttpd admin profile requires adding auths and creating a Profile entry. How do I add entries to the likes of prof_attr and auth_attr without using scripts? Maybe it's a discussion for another forum and I can just state the intent to create the Lighttpd Admin Profile and the auths that that requires in the Arc case. Also, an update on the other gap in the Arc case. Lighttpd builds all of the libraries for it's loadable modules even if support for a module or modules is not not enabled at build time (either through choice or because of a missing dependency). It's basically a conditional build and the lib files are just stubs in that they exist, but don't do anything. If you try to enable such a module at runtime through the Lighttpd config file, lighttpd fails with an error (which does indicate which module was the cause). It dlopen()s the library and then fails to find the symbol it's looking for in that library. When the library is removed , it comes back with a longer, scarier message saying that dlopen() failed for the module in question. I propose that we build with support for as many modules as possible, but leave any "stub" libraries in the distribution so that when trying to use a module that we don't have support for, users get back an error message that they can google for and get meaningful results back. Currently only 2 modules are affected, they are mod_magnet and mod_cml. mod_cml is being replaced by mod_magnet. The bigger deal is not having support for mod_magnet (requires Lua) as the Lighttpd folks say that this is a major feature of Lighttpd going forward. Amanda Jyri Virkki wrote: > Amanda waite wrote: > >> I asked the Lighttpd forum and had a couple of replies, both came people >> who had a high level of involvement in the Lighttpd community. One said >> that they rarely run the lighttpd executable directly, only when looking >> at issues. >> > > Sounds good, so I'd skip adding the link to the binary as it is not > needed for the common use cases of a daemon process like lighttpd. > That avoids your package having to worry about the link upgrade issues > so it is simpler. > > >
