Mailinglist Archive: opensuse-security (601 mails)

< Previous Next >
Re: [suse-security] NFS vs. cronjobs
  • From: alex medvedev <alexm@xxxxxxxxxxx>
  • Date: Fri, 4 Aug 2000 07:59:53 -0500 (CDT)
  • Message-id: <Pine.LNX.4.21.0008040756060.11317-100000@xxxxxxxxxxxxxxxxx>

sounds like the NIS server is not responding/rebooted at about 0:00 am
what does ypwhich say on the client when this happens?
why is it a security problem? :)


On Fri, 4 Aug 2000, Christian Mudra wrote:
> This ping was started directly after such a login - so you see, after
> about 2 1/2 min of just being logged in the network is back to normal.
> Logging in to such a slowed down machine is only possible as root,
> not as user (user authentification uses NIS). But as security policy
> we wanted to allow root login only via su, not remote, not on console.
> As long as this problem exists, at least root login on console must
> be allowed ...
> Additionally sometimes there are messages like that in the syslog:
> Aug 4 11:44:47 mycomp kernel: nfs: task 1674 can't get a request slot
> Aug 4 11:44:49 mycomp kernel: nfs: task 1681 can't get a request slot
> Aug 4 11:44:59 mycomp kernel: nfs: server OK
> So, my question is: How can I avoid these nfs-problems? Has somebody
> also experienced problems like this? And why does that begin on every
> client just after the cronjobs finished? Ideas?

< Previous Next >