[Spacewalk-list] Kickstart issues with user setup.

[BOWMAN MARK]

Can anyone suggest a way to action some user setup stuff during a kickstart?

The kickstart seems to stop at the su command.

.

.

/usr/sbin/adduser -p '$1$PYL05YxN$JwONw15qAMQrI5f1z45Sr/' smith

Would like to then:-

# su - smith

# mkdir --mode=700 .ssh
cat >> .ssh/authorized_keys << "PUBLIC_KEY"
ssh-rsa AAAAB3NzaC1yc2....

PUBLIC_KEY

Also looking for way to debug/log a snippet

I already have a:

% post --log-/root/mykickstart.log

It doesn't seeme able to capture of the snippet

Kind regards

Mark

[Coy Hile]

On Thu, Mar 29, 2012 at 8:16 AM, BOWMAN MARK <markb...@ntlworld.com> wrote:

Can anyone suggest a way to action some user setup stuff during a kickstart?

The kickstart seems to stop at the su command.

.

 

 

Why su at all?  You know what the defaults are for your systems.  why not do something like:

mkdir -m 0700 /home/smith/.ssh

chown smith:smith /home/smith/ssh
[put key material in authorized_keys here]
chmod 644 /home/smith/.ssh/authorized_keys

That seems more straightforward to me.  It's not like you actually need the user's environment; you're not starting a service dependent upon that environment.