linuxconf all changes logs

linuxconf all changes logs

Change log index

Version 1.21


Module accountbatch: New

The module accountbatch lets you maintain the user account database (/etc/passwd, shadow, smbpasswd) from another database. The module expect a file having the following format:

user-id   group   user-name  shell  password
Each field is separated by a tab. The module accept also the output of a command. From there, you can either add or delete accounts. Accounts found in the file, but not in /etc/passwd will be added. Account already in /etc/passwd won't be affected. Account in /etc/passwd and not present in the file will be deleted. When using deletion, you must specify on which groups the module is authoritative. It won't delete all account not found in the file: Only accounts member of specific group, or with a group id higher than a specified value.

The module has a test button, so you can safely try it and do nothing. Once you have process the file, you can use the module again and it won't do anything, since everything is in sync.

The module allows you to keep several configuration and replay them later (which file or command authoritative on which groups and so on).

Version 1.21r1


Module accountbatch: more features

There is now a help screen for this module. It describes among other things the file format it expects. There is also a new check-box. While updating the account database (/etc/passwd). you can update the password of existing accounts. This might be useful for schools wanting to reset all password at session start to a known one.

The module has now a progress dialog, with up to three gauges. One shows the creation process (new accounts), another the deletion and the last one, the password update process.

Version 1.26r1


Module accountbatch: command line option

The accountbatch module is used to add/remove/modify user accounts from an ASCII file. There were initially no command line to trigger an update. There is now. All features available from the dialog are now available from the command line. The man page has been updated.

The option --update has been added and it has many sub-options.

    --update [--test] [--silent] [--file path] [--group groupname ]
             [--grouplow gid ] [--add ] [--del ] [--mod ]
             [--archive ] [--delfiles ]

Version 1.26r2


Module accountbatch: virtual registry

Configuration of the module may be done using the virtual registry.

Version 1.26r5


Module accountbatch: Some enhancements

The module expects a file with 5 fields to create/maintain accounts. the fields are: user id, name, group, shell, password. In most case this information is not readily available. For example, many accountbatch user are getting their file from a school registry. They get only the userid and the name. The rest is missing, but can be often supplied as constant. A simple script fits the bill. This is nevertheless annoying. So the module was enhanced to accept various file format and supply default for missing field.

A section has been added to the dialog and for each field, we can specify the column in the input file. Or we can say it is missing in the file and supply the default value.

For the password field, we can request auto-generation of the passwords. If selected, the passwords are generated using random values and the report is produced at the end to collect the passwords generated.

A new button "preview" was added to preview the file content after applying the proper parsing. So you can tell if the module properly understand your file and supplies the proper defaults.

Version 1.27

Bug fixes

Module managerpm

The module was generating new password even if it was not needed. Those password were not used, but the module nevertheless was presenting a report about those generated modules.

The module is doing more validations prior to performing the task: Check if all groups exists for one.

Version 1.30r2


Module accountbatch: LDAP and extra fields

When you setup an LDAP database for user accounts, you often wish to enter more information about users: department number, The accountbatch module is using the inter-module API acctextra to learn about extra fields to supply to LDAP (Currently, only the ldapconf module implements this API).

The module accountbatch is able to parse the input file and assigns the extra fields to LDAP using the API.

Module accountbatch: smarter parsing

The module is used to create/maintain user accounts from a text file (usually produce by another database). The module can parse a text file and extract fields (userid, gecos, password,...) in various position on text line. It can now combine and format them. For example, if you have some numeric ID referencing a user, you can prefix it with a letter: a#2 will put a a prefix in front of the second field of the line.

It can also be used to combine two fields. For example, you may have the name and the surname as different fields in the input file and used them to setup the gecos field.

Version 1.31r1


Module accountbatch: deleting old configs

The module did not provide a way to delete old configuration. Now it does.

Version 1.31r3


Module accountbatch and LDAP

The module works with the ldapconf module to help populate the LDAP database, not only with basic user account stuff, but with user defined information. The module was able to create new accounts with extra information, but was unable to update existing accounts.

Further, the module was not able to update existing account under control. Now you can specify field by field, which one will be updated.

Bug fixes

Module accountbatch in text mode

The module had many problems in text mode. Sometime the display was completely broken. Oddly, this was not a problem with the module per see. The problem was in the UI toolkit. The module was simply pushing some limits a bit.

But it was only affecting accountbatch...

Version 1.32


Module accountbatch: supplementary groups

The module let you configure the supplementary groups of a user. (and this works in combination with the ldapconf module).

Version 1.33r6


Module accountbatch: various enhancements

The module has been enhanced to allow either disabling or deleting user accounts.

when deleting accounts, the module may execute a command ( authorization command) to learn the list of account it is allowed to delete. Normally, the module will delete/disable accounts on which it is authoritative (member of some groups only). But many tests accounts are created manually and the module can't tell them apart. Now you can write a script reading its standard input and producing on standard output the list of account ok for deletion.

When filling the "operate only on groups" field, you can enter simply a start ("*"). This means accountbatch is authoritative on all groups appearing in the input file. This is useful when the input file contains lots of users in different groups.

The dialog was a bit confusing. You had the test button to run a simulation and get the list of account added,updated, deleted or disabled. And you had the accept button performing the task for real. This button was replace with a "run" button place near the "test" button.

When using the command line to perform account creations or updates you can use the --config option to load one configuration. So you inherit all the parsing information stored with the configuration. Later you can still use the --file or --group (or any other option) to override the stored configuration settings.

Version 1.34


Module accountbatch: various enhancements

Various enhancements were made over 1.33r6:

  • Speed enhancement, especially when dealing with large account databases. It was tested with 40k accounts.
  • The report showing what will be/was changed now include exactly what was change. For each information, you see the old and new value. When updating tons of accounts, it is good to figure out what is going on (and validate your input file somewhat).

  • A new field "log file" let you enter the path of a file collecting all reports detailing changes done by accountbatch.

  • When performing an update, accountbatch was doing some validation and was producing interactive error message for each problem found. Further, it was stopping the processing there.

    Now, it collects all errors and presents a single message at the end of the add/update sequence. If there is one error found, the deletion/disable task is skipped.

  • When you view the status report, you can save it in a file.

Version 1.34r2


Module accountbatch: preserving the update fields

The module allows you to selectively update account fields. You check/un-check the various fields you want to update (gecos, home, ...). Previously the setting had to be entered prior to run accountbatch. Now the setting is saved with the configuration.

Version 1.34r3


Accountbatch: duplicate records

The module used to signal duplicates in input file and stop processing. Now it process only the first occurrence and signal the duplicates as warning in the result log. This save some time while processing large account sets.