Sponsored Content
Full Discussion: Ftpd alarms
Operating Systems Solaris Ftpd alarms Post 302927751 by jim mcnamara on Friday 5th of December 2014 07:54:35 AM
Old 12-05-2014
This means your chroot environment cannot see all of the files it needs to login. You need to create a more robust fake "/usr" file tree for the chroot jail. DO NOT use links, that defeats the chrooted jail.
 

10 More Discussions You Might Find Interesting

1. Solaris

Alarms/Alerts

Is there a imbedded command (Solaris v8 ksh) that will send an administrative alert/alarm. Or is it just triggering a mail message via shell script? If no, is there a good open-source code someone knows about? Thanks so much in advance for any replies. ...Gozer13 (3 Replies)
Discussion started by: gozer13
3 Replies

2. Shell Programming and Scripting

alarms

Hi I have been trying to set up alarms on my Solaris box (Sun OS 5.8) The objective is to present the user an audible alarm every hour or so. I have so far done this: #!/bin/sh val=1 while do printf "\a" val=`expr $val + 1` done I have put this in my crontab to run hourly.... (2 Replies)
Discussion started by: run_time_error
2 Replies

3. UNIX for Dummies Questions & Answers

Autosys Email Alarms

Hello, I'm kind of new to autosys, but I'm assuming there is a way to have Alarms be emailed instead of having to run jobscape and click the Alarm button to see what jobs have failed? Does anyone have an insight onto how this can be done? Thanks. (14 Replies)
Discussion started by: rpiller
14 Replies

4. UNIX Desktop Questions & Answers

how to check if a file ftpd to mainframe was actually ftpd

Hi All, I am ftping a file from unix to mainframe. Now the problem arises that i want to check if the file was ftpd or not. Is there any way i could do this? (4 Replies)
Discussion started by: vikas.rao11
4 Replies

5. Infrastructure Monitoring

Sun Solaris 9 Traps Contain Multiple Alarms

Hi all, I have a Sun Solaris 9 box which acts as a firewall. Sometimes if multiple actions which cause snmp traps occur very close together, a single snmp trap that is sent containing the text for multiple alarms. I would like to prevent that and have a trap sent for each action which would... (0 Replies)
Discussion started by: g0ld2k
0 Replies

6. Solaris

lp serverlist alarms in messages

Hello, I have been receiving following alarms in /var/adm/messages dtcp: WARNING DB (db_tcp.c,363) db_alloc_connid: lp && lp->serverlist error for service 20 It seems like this message is related to LP print service. Since I am not using any print service, is there any way to switch it... (2 Replies)
Discussion started by: aalishan
2 Replies

7. Solaris

Hardware Alarms on HP-ux Solarisx86

Hi I am trying to configure the Hardware alarms on HP server. I have refer to "HP ProLiant Health Monitor User Guide" and installed HPQacucli-3.5.0-solaris10-i386 HPQhealth-4.4.0-solaris10-i386 HPQhma-5.7.0-solaris10-i386 HPQilo-1.4.5-solaris10-i386 HPQsmh-5.5.0-solaris10-i386 ... (2 Replies)
Discussion started by: anand87
2 Replies

8. Solaris

Strange power supply units alarms!!!

Hi folks, I encountered this alarms on a solaris server: 04/21/12 23:17:55 MNP-PGW-A_bge3 mnp 231748 Power Supply Unit 0 is faulty 04/21/12 23:17:55 MNP-PGW-A_bge3 mnp 231748 Power Supply Unit 1 is faulty 04/21/12 23:18:26 MNP-PGW-A_bge3 mnp 231822 Power Supply Unit 0 is faulty:CLEAR... (0 Replies)
Discussion started by: kimurayuki
0 Replies

9. Solaris

Sudden Service Busy Alarms

Hi, I am getting service busy alarms on my machines which are using MongoDB every now and then. When the service busy alarm appears, I get the following errors on my mongo router logs. Tue Apr 7 08:01:08.445 dbclient_rs nodes.ok = true hxcslc-b05:27014 Tue Apr 7 08:01:08.445 dbclient_rs... (0 Replies)
Discussion started by: sni_engineer
0 Replies

10. UNIX for Beginners Questions & Answers

CentOs server generating several alarms on partition /proc/

Greetings, I have been facing one issue here and I am not understanding what is causing. I am getting a lot of alarms complaining that the partition for example /proc/12345 , is full, but the partition does not existe on the server. Which is not supposed to happen, because /proc is not a real... (10 Replies)
Discussion started by: Yagami_Sama
10 Replies
RSSH.CONF(5)							  Derek D. Martin						      RSSH.CONF(5)

NAME
/etc/rssh.conf - configuration file for rssh OVERVIEW
rssh.conf is the configuration file for rssh. It allows the system administrator to control the behavior of the shell. Configuration key- words are either used by themselves on a line, or followed by an equal sign ('=') and a configuration value. Comments start with a hash ('#') and can occur anywhere on the line. Configuration options are case insensitive. Spaces at the beginning or end of line, or between the equal sign and the configuration keywords or values are ignored. If the value of a configuration option contains spaces, it (or at least the space) must be enclosed in either single or double quotes. A default configuration file is provided with the source distribution of rssh. If the configuration file is missing or contains errors, ssh will lock out all users. If a config file is present, the default is to lock out users if no services have been explicitly allowed. New in v2.1 is the ability to configure options on a per-user basis, using the user keyword. More details are below. CONFIGURATION KEYWORDS
allowscp Tells the shell that scp is allowed. allowsftp Tells the shell that sftp is allowed. allowcvs Tells the shell that cvs is allowed. allowrdist Tells the shell that rdist is allowed. allowrsync Tells the shell that rsync is allowed. allowsvnserve Tells the shell that svnserve is allowed. umask Sets the umask value for file creations in the scp/sftp session. This is normally set at login time by the user's shell. In order not to use the system default, rssh must set the umask. logfacility Allows the system administrator to control what syslog facility rssh logs to. The facilities are the same as those used by sys- logd.conf(5), or the C macros for the facilities can be used instead. For example: logfacility=user logfacility=LOG_USER are equivalent, and tell rssh to use the user facility for logging to syslog. chrootpath Causes rssh (actually a helper program) to call the chroot() system call, changing the root of the file system to whatever directory is specified. Note that the value on the right hand side of the equal sign is the name of a directory, not a command. For example: chrootpath=/usr/chroot will change the root of the virtual file system to /usr/chroot, preventing the user from being able to access anything below /usr/chroot in the file system, and making /usr/chroot appear to be the root directory. Care must be taken to set up a proper chroot jail; see the file CHROOT in the rssh source distribution for hints about how to do this. See also the chroot(2) man page. If the user's home directory (as specified in /etc/passwd) is underneath the path specified by this keyword, then the user will be chdir'd into their home directory. If it is not, then they will be chdir'd to the root of the chroot jail. In other words, if the jail is /chroot, and your user's home directory is /chroot/home/user, then once rssh_chroot_helper changes the root of the system, it will cd into /home/user inside the jail. However, if your user's home directory is given as /home/user in /etc/passwd, then even if that directory exists in the jail, the chroot helper will not try to cd there. The user's normal home directory must live inside the jail for this to work. user The user keyword allows for the configuration of options on a per-user basis. THIS KEYWORD OVERRIDES ALL OTHER KEYWORDS FOR THE SPECIFIED USER. That is, if you use a user keyword for user foo, then foo will use only the settings in that user line, and not any of the settings set with the keywords above. The user keyword's argument consists of a group of fields separated by a colon (':'), as shown below. The fields are, in order: username The username of the user for whom the entry provides options umask The umask for this user, in octal, just as it would be specified to the shell access bits Six binary digits, which indicate whether the user is allowed to use rsync, rdist, cvs, sftp, scp and svnserve, in that order. One means the command is allowed, zero means it is not. path The directory to which this user should be chrooted (this is not a command, it is a directory name). See chroot_path above for complete details. For example, you might have something like this: user = luser:022:000010: This does the following: for the user with the username "luser", set the umask to 022, disallow sftp, and allow scp. Because there is no chroot path specified, the user will not be chrooted, regardless of default options set with the keywords above. If you wanted this user to be chrooted, you would need to specify the chroot path explicitly, even if it should be the same as that set using the chrootpath keyword. Remember that if there are spaces in the path, you need to quote it, something like this: user = "luser:022:000010:/usr/local/chroot dir" See the default rssh.conf file for more examples. SEE ALSO
rssh(1), sshd(8), ssh(1), scp(1), sftp(1), svnserve(8), syslogd.conf(5), chroot(2). man pages 7 Jul 2003 RSSH.CONF(5)
All times are GMT -4. The time now is 10:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy