Menu
▾
▴
Re: [webmin-l] bug?
|
From: Jamie C. <jca...@we...> - 2007-04-25 22:58:14
|
On 23/Apr/2007 21:49 Maxwell Smart wrote ..
<blockquote type="cite">
<pre>On 22/Apr/2007 22:44 Maxwell Smart wrote ..<br /></pre>
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> </span>On 22/Apr/2007 23:09 Maxwell Smart wrote ..<br /> </pre>
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> > </span>On 22/Apr/2007 03:50 Maxwell Smart wrote ..<br /> </pre>
<blockquote type="cite">
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> >> > </span>I think I found a bug. I thought I would mention it for consideration.<br /><span class="moz-txt-citetags">> >> > </span>
<span class="moz-txt-citetags">> >> > </span>I removed Proftpd from my Virtualmin configuration. in the "For module<br /><span class="moz-txt-citetags">> >> > </span>Virtualmin Virtual Servers (GPL)" section. I then did some other<br /> </pre>
</blockquote>
</blockquote>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>things<br /> </pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> >> > </span>and went to refresh the config and it said that the mod_suexec needed<br /> </pre>
</blockquote>
</blockquote>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>to<br /> </pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> >> > </span>be turned off in the server templates or turned on in Apache. I looked<br /><span class="moz-txt-citetags">> >> > </span>everywhere to turn it off in the server templates to no avail. I<br /> </pre>
</blockquote>
</blockquote>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>was <br /> </pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> >> > </span>giving up when I noticed that the Proftpd status on the system <br /><span class="moz-txt-citetags">> >> > </span>information page was no longer there even though it was running. <br /> </pre>
</blockquote>
</blockquote>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>I went<br /> </pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> >> > </span>back into the Virtualmin configuration and re-checked the Proftpd<br /> </pre>
</blockquote>
</blockquote>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>box it<br /> </pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> >> > </span>rechecked the config automatically and voila the mod_suexec issue<br /> </pre>
</blockquote>
</blockquote>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>was gone.<br /> </pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> >> > </span>
<span class="moz-txt-citetags">> >> > </span>How do I disable the mod_suexec in the server templates should the<br /> </pre>
</blockquote>
</blockquote>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>need<br /> </pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> >> > </span>arise?<br /> </pre>
</blockquote>
<pre><span class="moz-txt-citetags">> >> </span> <br /> </pre>
</blockquote>
<pre><span class="moz-txt-citetags">> ></span>
<span class="moz-txt-citetags">> > </span>It is on the 'Apache website' page - the 'Automatically add appropriate<br /> </pre>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>SuExec<br /> </pre>
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> > </span>directive?' field, which is just below the list of Apache directives.<br /> </pre>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>OK thanks<br /> </pre>
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> ></span>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre><span class="moz-txt-citetags">> >> > </span>My Proftpd status in the System configuration still doesn't show the<br /><span class="moz-txt-citetags">> >> > </span>running status of the ftp server even though it's running and accepting<br /><span class="moz-txt-citetags">> >> > </span>connections. Is there a fix for this?<br /> </pre>
</blockquote>
<pre><span class="moz-txt-citetags">> >> </span> <br /> </pre>
</blockquote>
<pre><span class="moz-txt-citetags">> ></span>
<span class="moz-txt-citetags">> > </span>Does it show up as running in the ProFTPd module? YES and configurable<br /><span class="moz-txt-citetags">> ></span>
</pre>
</blockquote>
<pre><span class="moz-txt-citetags">> </span>So you do see the 'Apply Changes' link in the top-right corner of every<br /><span class="moz-txt-citetags">> </span>page in <br /><span class="moz-txt-citetags">> </span>the ProFTPd module?<br /><span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>No just the Start ProFTPd link<br /> </pre>
</blockquote>
<pre><!---->
Ok .. it looks like Webmin is looking in the wrong place for the ProFTPd PID file.
In the ProFTPd module, click on the Module Config link and make sure the
'Path to ProFTPD PID file' is correct .. it should be something like /var/run/proftpd.pid .
- Jamie
Bingo,
The new ProFTPd installation puts it in the /usr/local/var/proftpd.pid folder and not the default /var/run/proftpd.pid It works like a charm. The apply changes are now there and the system info page is correct. :)
</pre></blockquote><span style="font-family: monospace;">Was this ProFTPd install you did yourself from source? I am guessing so .. which would explain why it uses a different PID file path from an OS-provided package. I generally recommend using the packages provided by your OS if possible, as the default module configurations are setup to match them..<br /><br /> - Jamie<br /></span><br />
|