I was running RH8 and I have a script to mount certain directories of a WinNT box to certain mount points. Everything worked fine until I "upgraded" to RH9. Now when I run the script it will die at various places and I have to run the mounts one at a time. I would run the script a boot so that the mounts would reattach in the event of a power failure. Life was good now it's just a pain in the a.s.s. Thinking of going back to RH8 .
Anybody else have or heard of this?

Cooner

Can you post the script?

here ya go!
#!/bin/bash

mount -t smbfs -o username=thisuser,password=userpass //poweredge/mc_reports$ /var/www/html/midco/reports
mount -t smbfs -o username=thisuser,password=userpass //poweredge/mc_lode$ /var/www/html/midco/lodedata
mount -t smbfs -o username=thisuser,password=userpass //poweredge/Midcont$ /var/www/html/midco/drawings
mount -t smbfs -o username=thisuser,password=userpass //misc001/midco_images$ /var/www/html/midco/images
mount -t smbfs -o username=thisuser,password=userpass //poweredge/uscable_dwg$ /var/www/html/uscable/drawings
mount -t smbfs -o username=thisuser,password=userpass //poweredge/us_reports$ /var/www/html/uscable/reports
mount -t smbfs -o username=thisuser,password=userpass //misc001/uscable_images$ /var/www/html/uscable/images
mount -t smbfs -o username=thisuser,password=userpass //poweredge/savage$ /var/www/html/sci/drawings
mount -t smbfs -o username=thisuser,password=userpass //poweredge/sv_reports$ /var/www/html/sci/reports

What kind of error message do you get when the script executes?

Copy of smbmount.log
[2003/07/28 12:23:30, 0] client/smbmount.c:send_fs_socket(383)
mount.smbfs: entering daemon mode for service \\poweredge\mc_reports$, pid=3040
[2003/07/28 12:23:31, 0] client/smbmount.c:send_fs_socket(383)
mount.smbfs: entering daemon mode for service \\poweredge\mc_lode$, pid=3046
[2003/07/28 12:23:32, 0] client/smbmount.c:send_fs_socket(383)
mount.smbfs: entering daemon mode for service \\poweredge\Midcont$, pid=3051

I suppose I should add that I get no error in the system messages file.
It just stops and you need to hit ctl/z to break out of it

can they be mounted in the terminal (ie using smbmount, via smbclient)?

You are saying that when you run the cammands manually, it works fine. But when you run the script when booting, it does not work.
Have you tried running the command after login?

just to add, if u "upgraded" in the true sense of the word to red hat 9 using the upgrade feature, then you are asking for problems, if you did a clean install you would likely eliminate a lot of your concerns.
let's hope u created some separate primary home and usr partitions, lol.

Well the "upgrade" as I called it was a complete reinstall (I never use anybodys upgrade). The problem happens anytime, ie.. running a script or running a single command in the terminal. Sometimes it works and somtimes it don't. I am starting to believe it may have something to do with the depth of the directories on the NT box though I still have an rH8 box this all works fine on. I have another box with RH9 that I just tried this on last night and I have the same problem.

What version of samba is it? Also did you try the smbmount command instead of mount?

Forgot, is your resolv.conf right? I have had some distros that that never set it up right at install and I had to do it manually. If you don't have the serach mydomain.com in it, it will cause you problems too.

samba 2.2.7a-8.9.0
The resolv.conf appears to be OK
No I have never tried smbmount command, I thought that was what I was doing with the options -t smbfs ?
Could you give me an example.

The smbmount was just a guess. Can you ping the NT server by name? Do you have any dropped packets when you ping?

Cooner, I had the same exact problem you are talking about when I went from 8 to 9.
Try doing this:
mount -t smbfs -o username=thisuser,password=userpass //poweredge/mc_reports$/ /var/www/html/midco/reports

Make sure you put a slash after the $, thats what ended up fixing the majority of the issues that I had, Also try adding a sleep 1 command betwwen them. They might be getting the signals hung up on the NT box.