__/ [SmakDaddy] on Monday 20 February 2006 13:45 \__
>
> "Roy Schestowitz" <newsgroups@xxxxxxxxxxxxxxx> wrote in message
> news:dtc1dq$2glf$1@xxxxxxxxxxxxxxxxxxxx
>> __/ [SmakDaddy] on Monday 20 February 2006 07:25 \__
>>
>> >
>> > "Roy Schestowitz" <newsgroups@xxxxxxxxxxxxxxx> wrote in message
>> > news:dtbqbp$2ec4$5@xxxxxxxxxxxxxxxxxxxx
>> >> __/ [Nospam] on Monday 20 February 2006 05:34 \__
>> >>
>> >> > I am wondering where precisely on cpanel I would run a script command
>> > such
>> >> > as this:
>> >> >
>> >> > mysql --user usernameofdatabase -p databasename < script-v.X.xx.sql
>> >> >
>> >> > I have tried running it in a sql query window in Myphpadmin
>> >>
>> >> First option is to use a cronjob hack, assuming your host gives you no
>> >> shell/Telnet/SSH access, but leaves cron jobs in tact. Instructions
> below:
>> >>
>> >> http://schestowitz.com/Weblog/archives/2005/09/12/cpanel-terminal-hack/
>> >>
>> >> The other is to install PHP-Shell:
>> >>
>> >> http://mgeisler.net/php-shell/
>> >>
>> >> it might become handy in the future.
>> >>
>> >> Hope it helps,
>> >>
>> >> Roy
>> >
>> > Most cpanel hosts enable cron's by default right from the control.
>> > Shell isn't needed to set.
>> >
>> > Not to step on Roy, but check you're host's TOS.
>> > If you install a phpshell, and it's not allowed, it could get you in
> deep
>> > with your host fast.
>>
>> Really? I never thought this would have any possible complications, given
>> that most operations are still not permitted. I noticed that my host
> started
>> running some monitoring system on February 14th, about 3 months after I
> had
>> installed phpshell:
>>
>> Running 'last':
>>
>> [...]
>> monitori pts/2 89.145.65.38 Fri Feb 17 06:32 - 06:32 (00:00)
>> monitori pts/2 89.145.65.38 Fri Feb 17 06:22 - 06:22 (00:00)
>> monitori pts/2 89.145.65.38 Fri Feb 17 06:12 - 06:12 (00:00)
>> monitori pts/2 89.145.65.38 Fri Feb 17 06:02 - 06:02 (00:00)
>> monitori pts/2 89.145.65.38 Fri Feb 17 05:42 - 05:42 (00:00)
>> monitori pts/2 89.145.65.38 Fri Feb 17 05:31 - 05:32 (00:00)
>> monitori pts/2 89.145.65.38 Fri Feb 17 05:21 - 05:21 (00:00)
>> [...]
>>
>> What could this be?
>>
>> Ta muchly for an opinion. I also noticed that spamassassin ceased to work
> on
>> the 14th. Could there be a conspiracy?
>>
>> Roy
>>
>
> They're monitoring for access on 89.145.65.38 which seems to be their
> application manager.
> SA not working? Best to contact them. They may have disabled due to SA
> overloads.
>
> Regarding 89.145.65.38, I was able to login with the default login.
Thanks, Smak. SA is back up (I informed them on Saturday). The load on the
system is rarely heavy, so I think it's merely a dying process on the box.
It happened a couple of months ago and I then informed the sysadmin, who in
turn got it fixed promptly. It sounds like it recurred.
Many thanks,
Roy
--
Roy S. Schestowitz | Useless fact: ~70% of organisms are bacteria
http://Schestowitz.com | SuSE Linux | PGP-Key: 0x74572E8E
3:20pm up 3 days 3:39, 7 users, load average: 0.84, 0.56, 0.60
http://iuron.com - Open Source knowledge engine project
|
|
