RE: post config files not executing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Title: RE: post config files not executing

Hi and thanks for you help so far. 
I answered my question, when you add the -nochroot to the %post command, bash is selected as the default shell.
I did have two dashes, but my Microsoft outlook changed them to one.  Wasn't that nice of Microsoft :)

So, I would like to just mount my own drive in %post and just work from there, but for some reason, it does not work.
when my %post gets to the mount command, I get these errors on one of the VTs:

portmap: server localhost not responding, timed out
portmap: server localhost not responding, timed out
lockd_up: makesock failed, error=-5
nfs warning: mount version older than kernel

Strange, the mount point is on the same machine (but different location) I'm mounting for my source media, that mount worked perfectly fine.

Second, I can mount the new exported directory from all my other boxes without error.  This looks like there is something wrong with the ks script!

after the script finally dies, I can go in and manually mount the drive, but it takes a __long__ time (like about two minutes).

Any ideas?

Thanks,
 -- Ryan


here is the script that is hanging:
###
%post

echo "Starting post install scripts!" >> /var/log/f5serverInstall
mkdir /f5
echo "mounting source directory" >> /var/log/f5serverInstall
mount 10.10.10.22:/f5server /f5




Ryan Allen
Senior Test Engineer
F5 NETWORKS
desk: 206 - 272 - 6538
fax:   206 - 272 - 5585
email: r.allen@xxxxxx

-----Original Message-----
From: Jason L Tibbitts III [mailto:tibbs@xxxxxxxxxxx]
Sent: Tuesday, December 04, 2001 11:47 AM
To: kickstart-list@xxxxxxxxxx
Subject: Re: post config files not executing

>>>>> "RA" == Ryan Allen <r.allen@xxxxxx> writes:

RA> 1.  (*) text/plain ( ) text/html

Please post in plain text.

RA> So if post runs with chroot /mnt/sysimage then it's impossible to
RA> get to /mnt/source without the --nochroot flag.  Am I right?

Correct.

RA> If you set -nochroot, then should %post -interpreter /bin/bash be
RA> relative to the nochroot?

If you pass "--nochroot" then the chroot is not done and you can
access things outside of /mnt/sysimage.

RA> In other words, what is correct:

RA> %post -interpreter /bin/bash -nochroot

RA> or

RA> %post -interpreter /mnt/sysimage/bin/bash -nochroot

I have no idea.  Picking nits, neither is correct because you need two
dashes in front of each option.  But I think you'll have to try it.

Honestly, I would recommend letting it do the chroot and doing the NFS
mount inside of the %post section as the manual suggests.  This makes
it much easier as you have access to the installed environment and
don't have to munge all of the pathnames.

 - J<



_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/kickstart-list


[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux