similar to: Hang when run via crond

Add -n to the ssh command line - see if that fixes it. Nico -- > -----Original Message----- > From: Eric Garff [mailto:egarff at omniture.com] > Sent: Wednesday, August 07, 2002 11:15 AM > To: openssh-unix-dev at mindrot.org > Subject: Re: so-called-hang-on-exit > > > That may be, but it only "hangs" when run from cron, if I run it > manually it executes

Perhaps the man page should be fixed then, because neither rsh nor rlogin provide any kind of port forwarding, or X11 forwarding, etc... Also, the comparison between ssh and rsh is more appropriate if you're talking about SSHv1 and much less so if you're talking about SSHv2. Nico -- > -----Original Message----- > From: Eric Garff [mailto:egarff at omniture.com] > Sent:

"It is intended to replace rlogin and rsh, and provide secure encrypted communications between two untrusted hosts over an insecure network." I can agree that it is "more" than secure RSH, but if it plans to replace it, shouldn't it have the same functionality? -- Eric Garff System Administrator egarff at omniture.com 801.722.0134 Omniture http://www.omniture.com

"ssh -n ..." means ssh will close stdin and open /dev/null for stdin. It does not mean losing th eoutput of ssh. Nico -- > -----Original Message----- > From: Eric Garff [mailto:egarff at omniture.com] > Sent: Wednesday, August 07, 2002 12:11 PM > To: openssh-unix-dev at mindrot.org > Subject: Re: Unrelated (was RE: so-called-hang-on-exit) > > > Sadly, no such

http://bugzilla.mindrot.org/show_bug.cgi?id=334 Summary: SSH hangs when run via a cronjob (ssh2) Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

http://bugzilla.mindrot.org/show_bug.cgi?id=334 egarff at omniture.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Additional Comments From egarff at omniture.com 2003-07-09 08:00

The RHL 6.2 command "/etc/rc.d/init.d/crond start" prevents clean logout from compiled version of OpenSSH-2.5.1p1 on all hosts. The command "/etc/rc.d/init.d/crond stop" is OK. This occurs for interactive or command line requests. ssh remotehost /etc/rc.d/init.d/crond stop --- works every time ssh remotehost /etc/rc.d/init.d/crond start --- hangs every time Control-C will

----- KSR[T] Website : http://www.dec.net/ksrt E-mail: ksrt@dec.net ----- KSR[T] Advisory #005 Date: Dec 6, 1997 ID #: lin-dcrn-005 Operating System(s): Slackware 3.4 Affected Program: dillon crontab / crond ( dcron

Hi All. I monitor number of crond processes on my machines. On one of them I have 2 crond processes for a short period of time (few minutes) everyday. It is at the same time when one jobs starts to run - a sphinx indexer. What are the possible causes of crond running a child crond process? Best regards, Rafal.

Hi guys: I could only find one answer for this topic via google, and the poster wasnt' sure if he was breaking something with his "fix". I there a way to redirect the cron session messages from syslog to a different log? i.e.: Aug 15 01:03:01 tn1 crond(pam_unix)[29303]: session opened for user root by (uid=0) Aug 15 01:03:07 tn1 crond(pam_unix)[29303]: session closed for user root

Hi, Just updated a few servers to U7, and rebooted them. I found out that crond would not start at boot even if it is configured to: crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off I have tested another reboot, same thing: I had to start crond manually. I don't see anything in the logs, and I don't have direct access to the console right now. Anyone seen the

Hi, I've installed CentOS-4 4 days ago. Now, every 5 minutes, crond opens and close a root session, with no other info. Example: Apr 14 16:25:01 tux crond(pam_unix)[4031]: session opened for user root by (uid=0) Apr 14 16:25:02 tux crond(pam_unix)[4031]: session closed for user root Every five minutes the same thing. I have nothing in /etc/crontab that makes such a thing. Does anyone

Hi, A couple of days ago, cron service stopped been running on my Centos 6. When I try to start with "service crond start" I get this error : "Starting /usr/sbin/crond: [-] Error 0x7a911401 in attaching to process!" Any ideas? Thanks

I have Cent OS 5.1 I also have http://phpsysinfo.sourceforge.net/ I have asterisk running . Now when I look at System Information , I see that "Physical Memory" keep increasing and at one point it reaches 96%. Then my sever get hang and then I have to restart it. I have 4 GB RAM. Processors 2 Model Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz CPU Speed 2.53 GHz Cache Size 3.00 MB

After startup of the DomU with xm create mydomu.cfg ­c The startup always stops, when starting the Cron-Daemon. [ 1.810477] EXT3 FS on xvda1, internal journal Loading kernel modules...done. Cleaning up ifupdown.... Setting up networking.... Activating lvm and md swap...done. Checking file systems...fsck from util-linux-ng 2.17.2 done. Mounting local filesystems...done. Activating swapfile

Hellos, Yes, I did some tests with "OnFailure" attribute, but the result was the same: system didn't sent any mail. Daemon and script files were: * crond.service: * [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target OnFailure=crond-notify-email.service [Service] EnvironmentFile=/etc/sysconfig/crond

A few times in the last couple months we have had our production Samba 3.0.14a-1server crash. We did not have detailed logging turned on at the time so the attached output of our log is the best process tracking I can give at the time of the crash. What will happen is our shares will no longer be accessible, and all the smbd processes will be hung. We can ssh to the server and do a restart

Alle, I'm running V5.3 (newly installed) on an FJ E8020 laptop. The problem I have is when shutting down (*not* rebooting). NetworkManager fails to stop and after (during?) the postfix shutdown, the system seems to hang. I cannot access via another screen or remotely. I can't find any clues in the log files. I could use some suggestions on troubleshooting. Here are the active

On Mon, 6 Apr 2020 at 06:59, Tobias Kirchhofer <collect at shift.agency> wrote: > On 6 Apr 2020, at 12:21, Stephen John Smoogen wrote: > > > On Mon, 6 Apr 2020 at 04:16, Tobias Kirchhofer <collect at shift.agency> > > wrote: > > > >> On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: > >> > >>>>>> we experience difficulties

> On Mon, 6 Apr 2020 at 06:59, Tobias Kirchhofer <collect at shift.agency> > wrote: > >> On 6 Apr 2020, at 12:21, Stephen John Smoogen wrote: >> >> > On Mon, 6 Apr 2020 at 04:16, Tobias Kirchhofer <collect at shift.agency> >> > wrote: >> > >> >> On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >> >> >>