> Thank you for your reply. It gave us options. We tried everything in > your post and nothing worked. Since the messages would only appear on > the HMC for a short period and then disappear I added a SLEEP 30s after > the "swapon -a -v &> /tmp/swaplog" command. This allowed us to see that > VFS had root mounted readonly and that the pipe to /tmp/swaplog failed > because it was readonly. I moved the swapon command further down in the > boot script (after fstab is processed) and everything is working. YAST > is the one that built /etc/rc.d/boot script and I am surprised that this > is not a more common problem. Maybe because I am using swap files > rather than a swap partition. > > We are still confused on where the messages go at IPL time. Several > replies pointed to dmesg, and boot.msg none of these had the messages > from our swap issue. Maybe because root is still mounted as readonly > and syslogd cannot write to the /var/log directory and the messages get > lost (just a therory). If anyone has any other theories please reply.
As I pointed out before, the redirection in the standard initialisation script sends messages to the Beautiful Bit Bucket in the Sky. Until you fix that problem by making the change I suggested, there is no prospect of the messages appearing anywhere at all. > > Running SuSe 2.2.16 > > Larry Hanus > Systems & Software Support > Sprint > > -----Original Message----- > From: mark.post [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 01, 2002 2:56 PM > To: LINUX-390 > Cc: mark.post > Subject: Re: Swap not starting > > Larry, > > The /etc/rc.d/boot script does start LVM before doing the swapon > command, so > you should be fine there. Still, you might try changing your swap > volume to > a swap file on the root file system and see if you still have the > problem. > > If you don't want to do that, try changing /etc/rc.d/boot so that > you have a > "set -x" command right after the 'echo "Running $0" line. That > will turn on > "print command" mode for the rest of the script. I would also > change the > "swapon -a -v &> /dev/null/" command to read "swapon -a -v" or, > perhaps > "swapon -a -v &> /tmp/swaplog" > > For your Samba problem, I've found that the 2.2 version doesn't > log as much > as it should. Put a "log level = 1" in your /etc/smb.conf file > before your > next reboot. If you bump the number up, Samba gets increasingly > verbose. > You probably won't have to go beyond 2 or at most 3 before you get > far more > output than you really want to see. > > Mark Post > > -----Original Message----- > From: Lawrence Hanus [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 01, 2002 3:12 PM > To: [EMAIL PROTECTED] > Subject: Swap not starting > > > I am a mainframe'er fairly new to the Linux world looking for some > help. > We are experiencing several startup problems at boot time. In our > /etc/rc.d/boot script we have "swapon -a -v &> /dev/null/' > (without the > quotes). We have also added echo statements to make it visible on > the > HMC during IPL. The echo statements are seen but there no > messages for > the swapon command (even with the added -v). /proc/swaps shows > nothing. > Our fstab has the following: > root@KDLNXT01:/etc > cat /etc/fstab > /dev/dasda1 / ext2 defaults 1 1 > /dev/dasdb1 /usr ext2 defaults 1 2 > none /proc proc defaults 0 0 > /dev/dasdc1 /vol1 ext2 defaults 0 1 > /dev/dasdd1 /vol2 ext2 defaults 0 1 > /dev/dasde1 /vol3 ext2 defaults 0 1 > /vol1/swap/swapfs1 swap swap defaults 0 0 > # End of YaST-generated fstab lines > > When I do a "swapon -a" after the IPL all swap datasets are > active. My > theory is that the swapon from boot script is failing maybe > because the > volumes are not fully mounted when the command is started. We > have > entered it in boot.local and everything works. Questions: > #1. Is there a reason why swapon command is not working from boot > script, but works from boot.local. > #2. After the echo messages appear on the HMC console, is there a > way > to make them appear in a log somewhere. I check boot.msg, warn, > messages, allmessages and grep the whole /var/log directory and > found > nothing. We are also experiencing problems with samba startup. > Sometimes it starts, sometimes it doesn't. We can never find any > messages. Samba is started in our /etc/rc.d/rc3.d/S91smb link. > What do > I need to know to find these messages. > > Thanks, > > Larry Hanus > Systems & Software Support > Sprint > -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition. ============================== If you don't like being told you're wrong, be right!
