user3146's questions

When I run the following command (as root or via sudo) from a bash script I get an exit status (or return code in mount man page parlance) of 1:

mount -v -t cifs //nasbox/volume /tmpdir/ --verbose -o credentials=/root/cifsid &> /tmp/mylog

It outputs the following into the myflog file:

parsing options: rw,credentials=/root/cifsid

mount.cifs kernel mount options unc=//nasbox\volume,ip=192.168.1.1,user=root,pass=xxxx,ver=1,rw,credentials=/root/cifsid

It mounts the volume fine but returns the exit code (from the mount man page):

1 Incorrect invocation or permissions

The standard Linux log files don't contain any error information. Hence, all seems to go well but I get an exit code of 1 instead of 0. Any ideas?

The -v and --verbose options are just there for debugging this problem.

Historically, I've always upgraded my hardware and software together. In short, since I've always had new hardware I've always installed the latest distribution version from scratch. This time, however, I don't need to upgrade my hardware but I do want to upgrade my distribution to one that is still supported, i.e. receives security updates, etc. Currently, I run Postfix and Cyrus-IMAP on a Fedora 8 server. I'm considering upgrading to the new Fedora 11 (when released). I know how to set up Postfix and Cyrus-IMAP and I have good backups of all the configuration data and the actual mail so I'm not overly concerned about losing anything or getting myself into a situation that I can't get out of. What I don't have a lot of experience with is during the install process choosing the "Upgrade" option instead of the "New Install" option. My concern is that an upgrade may screw up anything from SELinux to apache (I run squirrelmail also) to who knows what in such a subtle way that I don't realize it for some time, e.g. security holes, etc. Does anyone have experience using the upgrade option and if so what do I need to be especially aware of?

This server actually provides a couple of different services but the mail service is the critical one.

I have a Linux based (Debian 5.0) NAS that I need to shutdown reliably. When ssh'd into the NAS box I issue the following command:

sudo shutdown -h now

I've also tried 'poweroff' and su'ing into root and running the commands with the same results. It shuts down all the processes and everything fine but does not always 'halt' the system. I need it to power down into the S3 state so that I can reliably use Wake On LAN to start the unit as needed. For what it's worth, wol works great and works every time as long as the unit is in it's S3 state.