By 'client', do you mean the person/company paying you or client software?
If it's the former, tell them that they will not be supported, or perhaps get them to run the stop script as root.
If it is client software, then presumably somewhere there is a root-owned & SUID executable somewhere that is called in the start-up. Find that and take away the SUID.
Does that get you any closer?
Robin
Client as in my company. Who is running the daemon as non root when its not really needed. I've seen several implementations of this product but never seen the daemon running as root.
Hello,
First let me start by saying I have searched the forum and read all the SUID stuff but it is not in the neighborhood I am looking for.
Here is the problem. We want to grant a non super-user permission to kill root processes but only if the process matches certain criteria. ... (8 Replies)
hi,
I have a SCO unix server which has a 36gb hard drive, but the IT company who supplied it assigned 1gb to /dev/root, 15mb to /dev/boot and 33gb to /dev/u.
The /dev/root partition is now full, is there a way I can use the 33gb assigned to /dev/u without loosing any data, preferably... (2 Replies)
i have a very short file that has in it a line for a find command.
now, when i run this script and I kill the script later, using the ps -ef | grep scriptname. i noticed kill -9 kills the script itself but does not kill the internal find command that it gave birth to.
say theres a file... (0 Replies)
Hello,
ps -C a*
returns the list of the process I need to kill.
but
ps -C a* -o pid | kill
does not work and I can't get the syntax right.
Thanks for any help (4 Replies)
how to kill the processes of aperticular user?
because i have nearly 25000 process are there for perticular user. i need to kill.
Please provide the information?
Regards,
Rajesh (3 Replies)
Hi,
How to kill the processes running under ptree ?
I am noticing lot of processes running under ptree with ssh ? I tried to kill with -9 option which is not working ?
Thanks,
Radhika. (2 Replies)
for i in 'ps -f | grep textedit'
do
kill $i
done
I wrote this but it wont work.
I am trying to find processes and kill them.
Any help would be welcome. (1 Reply)
Hi there, i've been searching all over and i thought i had understood the way i should go to kill all the processes related to a user. But i'm getting more confused then i was.
By lunch time i have to make a database backup, and for that all the users shoul logout. The problem is that many users... (4 Replies)
Want to kill multiple processes by name. for the example below, I want to kill all 'proxy-stagerd_copy' processes.
I tried this but didn't work:
>> ps -ef|grep proxy_copy
root 991 986 0 14:45:34 ? 0:04 proxy-stagerd
root 1003 991 0 14:45:49 ? 0:01... (2 Replies)
Is there a way to find out the total no of processes that were running ?
- 2 or 3 hours before
- list those no of processes (3 Replies)
Discussion started by: jansat
3 Replies
LEARN ABOUT DEBIAN
saslfinger
saslfinger(1) General Commands Manual saslfinger(1)NAME
saslfinger - A utility to collect SMTP AUTH relevant configuration for Postfix
SYNOPSIS
saslfinger [-chs]
DESCRIPTION
saslfinger is a utility to collect SMTP AUTH relevant configuration for Postfix. Depending on how you run it, it will search for informa-
tion on server-side or client-side SMTP AUTH configuration settings in Postfix and Cyrus SASL.
OPTIONS -c If you run saslfinger with the option -c it will collect data required for client-side SMTP AUTH. Client-side SMTP AUTH is when
Postfix smtp daemon uses SMTP AUTH to authenticate itself with a remote mail server that offers SMTP AUTH.
saslfinger will try to telnet to all hosts listed in smtp_sasl_password_maps, if it may read smtp_sasl_password_maps
The telnet test verifies your host is able to reach the remote servers and shows what AUTH mechanisms they offer - in some cases
this is required to debug client-side SMTP AUTH.
Important: By default smtp_sasl_password_maps must be read-only to root, since these maps contain the usernames and passwords to
authenticate. If you run saslfinger as root access will be no problem, but saslfinger will fail if you lack the permissions to
access smtp_sasl_password_maps.
If you want to run the telnet test, but don't want to run saslfinger as root change permissions of smtp_sasl_password_maps so that
the user running saslfinger may access smtp_sasl_password_maps while you debug.
*note: You don't need to worry about saslfinger doing anything with the username or password stored next to the remote hosts in your
smtp_sasl_password_maps; saslfinger completely ignores these informations!
-h If you run saslfinger with the option -h it will print a little help message that tells you about the options you can use.
-s If you run saslfinger with the option -s it will collect data required for server-side SMTP AUTH. Server-side SMTP AUTH is when
Postfix smtpd daemon offers SMTP AUTH to mail clients.
FILES
saslfinger - the script you need to run.
saslfinger.1 - the man page you are currently reading.
AUTHOR
Patrick Koetter, <patrick.koetter@state-of-mind.de>, http://www.state-of-mind.de
You will find the newest version of saslfinger at http://postfix.state-of-mind.de/patrick.koetter/saslfinger/.
BUGS
Please report bugs to <patrick.koetter@state-of-mind.de>
Manuals User saslfinger(1)