| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 13/06/12 01:21 PM, Ian Stakenvicius wrote: |
| 5 |
> On 13/06/12 01:19 PM, Michał Górny wrote: |
| 6 |
>> On Wed, 13 Jun 2012 12:00:16 -0400 Ian Stakenvicius |
| 7 |
>> <axs@g.o> wrote: |
| 8 |
> |
| 9 |
>>> + ### force updates of some user properties + |
| 10 |
>>> usermod -d "${ehome}" "${euser}" || die + usermod |
| 11 |
>>> -s "${eshell}" "${euser}" || die |
| 12 |
> |
| 13 |
>> I think usermod can handle multiple arguments. |
| 14 |
> |
| 15 |
> |
| 16 |
> It can, but I figured it would be easier to debug if something |
| 17 |
> failed, if each modification was on the same line. Easy to modify |
| 18 |
> it to be a one-liner, however (and iirc all but possibly dscl can |
| 19 |
> do this in a single call) |
| 20 |
> |
| 21 |
> |
| 22 |
> |
| 23 |
|
| 24 |
As a follow-up to this, I believe it may be possible that my |
| 25 |
suggestion is incorrectly coded when considering cases where shell and |
| 26 |
home are not specified. IE, the updates should be called |
| 27 |
individually, and should only be called if their respective variable |
| 28 |
($ehome, $eshell) is actually set. |
| 29 |
|
| 30 |
I will post an update after some testing. |
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 33 |
|
| 34 |
iF4EAREIAAYFAk/Y37gACgkQ2ugaI38ACPB+RgD/a4qmpDYsTDCsgvsFmBSMnS9h |
| 35 |
CWID5XVVGTPduEcqKeQA/jvpFyDuEd4zh5pSe/fPinq7xLw5lufy+rXq8nxcRsJm |
| 36 |
=UofV |
| 37 |
-----END PGP SIGNATURE----- |
Archives