10-03-2007
As root, issue the following command
/etc/init.d/sendmail stop
To restart it:
/etc/init.d/sendmail start
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Am having trouble trying to stop the process below ...
bash# ps -eaf | grep "tape erase"
root 29715 1 0 05:16:22 ttyp1 00:00:00 tape erase /dev/rStp0
root 22464 20933 1 03:40:12 ttyp6 00:00:00 grep tape eraseI've tried ... `kill -9 29715` ... but still no luck.
Help... (8 Replies)
Discussion started by: Cameron
8 Replies
2. HP-UX
Hi all, I have problem in my HP Unix 11 server . my problem is :
When I try to telnet it, it gives me this error " connection refused by remote host" I asked one of my friends he told me you have to start telnet service and he did that by executing command like this " inited -c " or some thing... (1 Reply)
Discussion started by: KSA
1 Replies
3. UNIX for Advanced & Expert Users
Hi ,
I have one question, suppose i am a normal user and when i use 'w' command , it shows who is logged on and what they are doing .
Now i want to stop others users to know what i am doing accept the root ?
can i do this ?
thanks (5 Replies)
Discussion started by: mobile01
5 Replies
4. Solaris
Hi All,
I need to stop sendmail from running on boot-up. How can I do this on Solaris 8 and 9 sparc?
Please help and that you in advance. (2 Replies)
Discussion started by: itik
2 Replies
5. Solaris
sorry i got this already... (3 Replies)
Discussion started by: itik
3 Replies
6. Solaris
I am using solaris x86 with a pc keyboard. i am trying to get to the ok prompt i have tried ctrl-break but it is not working , alt-break will not as well.
pls any thought? (4 Replies)
Discussion started by: seyiisq
4 Replies
7. Red Hat
I have a user ( and actually me too) getting this messages when the screen is idle, I need help on stopping this messages:
2012 Feb 20 13:30:22 servername Audit: LENGTH: "330" SESSIONID: "339384" ENTRYID: "1" STATEMENT: "1" USERID: "OPS$PT2ADM" USERHOST: "zzzzzzzzzzz" ACTION: "100" RETURNCODE:... (2 Replies)
Discussion started by: 300zxmuro
2 Replies
8. UNIX and Linux Applications
Hi,
I am tearing my hair out, here. We have a CentOS 4.7 box running sendmail 8.13.1.
I can't send e-mail out from that box to anywhere not on localhost, as I keep getting the error 'DSN Data Format error', and 'A real domain name is required to send e-mail'.
I have edited the... (3 Replies)
Discussion started by: davidm123SED
3 Replies
9. UNIX for Advanced & Expert Users
I am running SCO 5.0.6 and using sendmail 8.11.0 and having issues with smtp authentication. When trying to send mail the following message will kick back.
(reason: 530 5.7.1 Authentication required)
530 5.7.1 Authentication required
Not sure what needs to be tweeked in sendmail.cf but I... (1 Reply)
Discussion started by: ziggy6
1 Replies
10. Solaris
Hi all,
I have read about sendmail running as 2 separate process.
1 as a MSP, and the other as the real daemon or MTA.
In my current configuration,
the sendmail-client is disabled.
Both submit.cf and sendmail.cf are left as default untouch
I do not specified any mailhost... (3 Replies)
Discussion started by: javanoob
3 Replies
LEARN ABOUT PLAN9
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)