Date: Wed, 8 May 1996 19:01:30 -0700 (PDT) From: Jim Dennis <jimd@mistery.mcafee.com> To: tomhavbe@martin.luther.edu (Benjamin Tomhave) Cc: questions@FreeBSD.ORG Subject: Re: Update: HELP! Message-ID: <199605090201.TAA13171@mistery.mcafee.com> In-Reply-To: <Pine.HPP.3.92.960508105006.25631G-100000@martin.luther.edu> from "Benjamin Tomhave" at May 8, 96 11:03:14 am
next in thread | previous in thread | raw e-mail | index | archive | help
> Ok....here's what I know....the problem is still here, but we may be > targetting in on the actual problem now. > > First, by "login problem" I mean this: you enter your username, you enter > your passwd, it says "Login incorrect". That's all. If you use rlogin > from an account w/ same username as account on the FreeBSD machine, you > get all the way in, execept it dies with some sort of error (I didn't get > to see this first-hand...one of my assistants tried this) about failing to > execute the shell. You also get a setlogin() error. > > Ok....at boot-up time this error occurs: > > NOQUEUE: SYSERR (root): getrequests: cannot bind: Permission denied > problem creating SMTP socket Sounds to me like smap or sendmail needs to be SUID root (to bind to the low numbered smtp port (25)). If this happens even when you are root, it might be that sendmail is owned by the wrong user/group. > This is all in reference to starting sendmail, which does not start. You > can ftp into the machine (non-anon, we don't support anon). You can login > from the x-console. You cannot login from any other terms, including any > of the other 3 virtual consoles. > > Some more errors to report are....when trying to do 'w' from any account > other than root I get: /dev/mem: Permission denied. Ok. So, I changed > the permission on that file and then it says /dev/kmem: Permission denied. Sound like more ownership/permission problems -- does FreeBSD need to be SGID kmem (or something like that). > Any ideas on that? Probably of lesser important. But, then I ask myself, > what are the permissions on most files in that directory??? I dunno if > they are right. Oh, btw, I have two files, /dev/rsd0.ctl and > /dev/rsd1.ctl. Each one is supposedly 536MB in size, yes I only have a > 800MB hard drive. Hello?!? What's up with that??? /dev/ entries aren't regular files -- they are devices (specifically they are links to devices which allow Unix to treat devices as "files" for purposes of programming abstraction). The sizes reported are not "additive" to the file sizes reported by other files. specifically these are the "raw" nodes (links). There should be corresponding "cooked" links named /dev/sd* If you want to actually find the amount of filesystem space consumed by a set of files use the 'du' command (disk usage report). If you want to know how much space is available on your filesystems use the 'df' command (disk free report). For the most part my advice is to leave the "files" in the /dev and /proc directory trees *alone* until you know much more about them (I leave them alone in any event). *VERY BAD THINGS HAPPEN* if you remove or modify these "files." > > This is a summary of the many problems I am encountering. Any suggestions > will be accepted gratefully. I need to get this machine up and running in > a stable state as we hope to use it next Fall for many things, and we must > have a reliable machine for those functions. > > Thanks for your help and patience! It sounds like you did something after the basic install. The FreeBSD 2.1 installations scripts (from the CD at least) would have set all the permissions and file ownership correctly. I'd recommend that you re-install from scratch. You could probably find and surgically fix the couple of problems that you described -- but I'd be really worried of what else was broken (particularly since some of the values of "broken" lead to nasty security problems). > -ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605090201.TAA13171>