Linux 9

glammers · 04-22-2004, 11:44 AM

I am a newbie to this website and to Linux 9 Install process. I have completed the install on my PC as a Workstation. Testing was going well, using different kinds of Linux commands and applications like Users and Groups, File Roller, Text Editor, and shell prompt commands.

In testing, I used the fsck command and got some messages, rebooted the system and got some other messages that I replied yes to and was able to boot up again. Everything seemed to be working the same except for the AT command. The repair work on permissions and making sure the ATD was started has got around initialization startup messages, now instead of atd [failed] get [ok].

The problem now is, I can create the AT command but the timer doesn't pop. If I do atq it displays showing a valid time before the date time
and in directory /var/spool/at I see the entry there ... time goes by and the
AT command does not run.

Then I use atrm n (n=the number) and it deletes ok.

Can someone point me in the right direction!!! Help!!! There was no
CD-ROM/RW on this PC to do backups!! Need a solution, or it will be a
pain to reinstall it all over again ....... Thanks.

Caeda · 04-22-2004, 11:51 AM

"Linux 9 Install process"

Wow, Linux 9 huh? That narrows it down to a couple dozen distros...

That little word.. Redhat, Mandrake, Suse, whatever little thing it says, you know they put that there for a reason? The reason being, its the brand name of whatever you chose to install and other people might need it?

glammers · 04-22-2004, 11:57 AM

RedHat is the Vendor....

glammers · 04-29-2004, 09:27 AM

Did not get any replies to my question. Finally had to backup some files to be restored, and reinstalled Red Hat Linux 9 again, restored from floppy disk what I could. Rebooted the system and the AT command is now working like it did before problem with using "fsck" command. From what I could see, it looks like the problem had to do with creating the directory in /var/spool/at for AT using root verses the reinstall creating the directory as AT using daemon. Permissions could have also caused some issues in it running correctly. This newbie has gone through the initiation - God Bless America!!!