If you have installed webmin somewhere else, you will have to change the /usr/libexec/webmin part of the path above. Restart inetd to make the changes take effect. You should now be able to access webmin on port 10000 as normal. Using the Bootup and Shutdown module, make sure that inetd is configured to start at boot time, and that webmin is not. If you have installed webmin somewhere else, you will have to change the /usr/libexec/webmin part of the path above.

Yes, this can be done with some configuration. See this document for details on running Webmin under Apache, or this page for details on running Usermin. You can also run Webmin under the Zeus webserver in a similar way. See this documentation for instructions.

If you have installed the RPM version of Webmin, you can also use rpm -e webmin, or if you have installed the Solaris package you can use pkgrm WSwebmin .

WebMin is an administration tool running on the Collector. To access it, use the WebMin icon on the Viewer desktop or through Internet Explorer go to URL http://(IP address):100000, for example http://10.1.206.111:10000. WebMin allows nearly full access to the Collector. It allows configuration of IP addresses, time/date, and many other items. You can do almost everything you could do with a monitor/keyboard/mouse on the Collector.

Yes, read Exploring Expect, Chapter 17 (Background Processing). In the section "Expect as a Daemon", there's a very thorough discussion of this problem and how to solve it. In short, there's no tty when you run a process from inetd. Echoing is controlled by the telnet protocol, so you must send and expect telnet protocol packets to solve the problem. Even knowing this, the actual implementation is very non-obvious which is why the book goes into it in such detail.

It is possible to install the ZIP package of Webmin on Windows using the included setup.pl script. However, this is extremely alpha-level code, and only a few of the Webmin modules work due to packages like Squid, Sendmail and so on not existing under Windows. In addition, the Windows security and permissions systems are quite different from Unix, so anything that deals with file ownership and modes may not work.

Included with the Webmin distribution is a program called changepass.pl to solve erecisely this problem. Assuming you have installed Webmin in /usr/libexec/webmin, you could change the password of the admin user to foo by running /usr/libexec/webmin/changepass.pl /etc/webmin admin foo

Just installing Webmin will not cause any config file changes to be made. When you start to use it, only the config files related to the changes that you make in Webmin will be modified. For example, using the Apache Webserver module would not effect your Sendmail configuration. If you are using SSL, make sure you connect to a URL like https://myhost:10000/ instead of http://myhost:10000. Without the https, your browser won't use SSL mode and thus will display this error.

By default, basic logging is enabled in Webmin. To turn on full logging, go into the Webmin Configuration module, click on the Logging icon and turn on the Log changes made to files by each action option. This will record all file changes and commands run by Webmin. Once logging is enabled, all actions performed from then on can be viewed in the Webmin Actions Log module. Your browser has automatically gunzipped the file for you. Just rename it to webmin-1.400.

In the Webmin Users module, click on the user that you want to symchronize with Unix and set his Password option to Unix Authentication. If PAM is not used on your operating system, the first two steps can be skipped. Webmin will instead read the /etc/passwd or /etc/shadow file directly to authenticate users who are using the Unix Authentication password mode.

In the Webmin Users module, create a new user called something like unixer, with access to the modules that you want all your Unix users to have access to. In each of the modules unixer has access to, change the module access control to give your users rights only to their own accounts. For example, in the Change Passwords module you should select Only this user for the Users whose passwords can be changed so that Unix users logging in can only change their own passwords.

By default, Solaris doesn't allow packages to be upgraded. However, you can change this by editing the file /var/sadm/install/admin/default and changing the instance= line to instance=overwrite. An upgrade can then be performed by simply installing the new Webmin .pkg file. By default, when a user composed email the From field contains username@systemhostname.

If you have the wrong version of Perl you will get errors similar to the following: syntax error in file /opt/hpapache2/webmin/miniserv.pl at line 6, next 2 tokens "use Socket" syntax error in file /opt/hpapache2/webmin/miniserv.pl at line 41, next 2 tokens "\Net:"

Maybe. While the use cases for building cron functionality into Upstart are clear, the use cases for building inetd functionality into it aren't. So far the principal reasons for doing so seem to be the perceived similarity between inet services and ordinary services, and because Apple's launchd happens to do it. I'm not convinced that the first is true; inet services while superficially similar to ordinary ones, are actually quite different.

Services formelery provided by inetd itself (called internal services) are still provided by inetd and can not be converted with inetconf.

The file you need to modify is /etc/webmin/miniserv.conf , in particular the allow= or deny= lines. If the allow= line exists, it contains a list of all addresses and networks that are allowed to connect to Webmin. Similarly, the deny= line contains addresses that are not allowed to connect. After modifying this file, you need to run /etc/webmin/stop ; /etc/webmin/start for the changes to take effect. Naturally, the file can only be edited by the root user. Edit the file /etc/webmin/webmin.

If you have a firewall that transparently proxies outgoing HTTP requests (such as one by Sonicwall), this may cause requests made by Webmin to by timed out. Without going into the underlying protocol details, my investigation has shown that Sonicwall is making incorrect assumptions about the number of IP packets an HTTP request will be in, and is thus broken.

In the Webmin Servers module, create a new user and give him access to only the Apache Webserver module. After saving, click on Apache Webserver next to the user's name in the list of Webmin users and use the form that appears to deny him access to everything except one selected virtual server. Many other modules can also be configured in a similar way to restrict the access of a user to only certain DNS domains, Unix users or mail aliases.

Webmin is a *nix ( ie. Linux, FreeBSD, OpenBSD, Solaris, etc. ) server control panel that can be accessed through the internet by a web browser. It provides a nice user friendly interface to most of the commonly used services on your server. To install webmin, follow the instructions here. There is no charge for installing or using Webmin.

On OS X, I keep getting Expat must be installed prior to building XML::Parser and I can't find it in the standard library directories

To release the a specific file (mail) from quarantine you can use the sendmail wrapper (/usr/sbin/sendmail /usr/lib/sendmail):

The MPP Webmin module is fully compliant with the Webmin standards for installation. It ships as a .wbm file and it is added by simply adding module in the module configuration section of Webmin. Back To Top

Yes. Webmin does very little date processing, and all that it does will continue to work properly after 1/1/2000. However, be aware that some of the servers that Webmin manages (such as Apache, Sendmail, etc..) may not be Y2K compliant if you are using older versions.

Webmin normally runs on port 10000, like 'http://example.com:10000/'. Sometimes you can configure webmin to connect via SSL through and stunnel setup or an open-SSL setup. More information on webmin can be found at the webmin website at:

The time interval in seconds between a failed bind attempt and a retry. The values 0 and -1 specify that no retries are attempted and the first failure is handled the same as exceeding bind_fail_max. The maximum number of times inetd retries binding to a service's associated port before giving up. The value -1 specifies that no retry limit is imposed.