Search results for query: *

the main impact i would be concerned about is having people with enough knowledge to be dangerous screwing your system and needing you to put it back together again. look for a utility called sudo. it allows you to run root commands as the user and it also allows logging so you can keep an eye...

you have to make sure the inetd process is running. how it works is the file /etc/inetd.conf contains a list of services that can be invoked like ftp, telnet, samba services and so on. poke around with the file and make sure that telnet is there. this file is used by the inetd process which...

1. edit /etc/inetd.conf and make sure telnet isn't hashed out. if it doesn't exist put it in as per the example above 2. edit /etc/services and make sure a port is specified for telnet to run (as per the example above) 3. ps -ef | grep inetd. note the process ID. 4. kill -HUP whatever the...

may be easier to just set up a cron job to blow them away rather than find the source of them and stop it logging in the first place

make sure telnet in enabled in /etc/services and /etc/inetd.conf the inetd.conf entry looks like this on my solaris 8 box telnet stream tcp6 nowait root /usr/sbin/in.telnetd in.telnetd and under services the telnet entry is telnet 23/tcp

check hardware 1. is the lan cable ok? intermittent problems may be coming through loose crimping or whatnot. make sure the user isn't twiddling with the cable. reminds me of a site i went to years ago that layed those spiky chair mats over the co-ax lan cable! 2. try a different switch port...