Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators For the Admins, rouge advert(s)... Post 302977685 by wisecracker on Thursday 21st of July 2016 07:25:48 AM
Old 07-21-2016
For the Admins, rouge advert(s)...

Hi guys this problem exists on all my machines...
Windows 8.1, Ubuntu, iMac and this MBP.
All use fireFox, latest current version.

If I log in there is NOT a problem.

I usually enter this site as an outsider and I have noticed that there is some rouge code and/or advert that slows the machines down to almost stop.

I thought it was malware but it occurs only from this site.
I would have expected any malware to affect facebook and other memory/disk hungry apps but everything works as it should.

Before sending this I tried my mum's Windows Vista, running current FireFox, machine, today 21st July 2016, 12:15pm UK local time, and it is still present...

To me it looks like video style advert overload and even with mum's BT-Infinity broadband the machine is unable to cope after several clicks onto different questions.

Remember that most people that need WWW unix searches get steered to here often and if this situation is affecting me it will affect them too.
 

6 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Admins >

Just wanted to say great website and thank you... (0 Replies)
Discussion started by: 98_1LE
0 Replies

2. UNIX for Dummies Questions & Answers

rouge processes

Often when i do a ps -ef |grep user there are sh processes however the users are not actually logged in. Does any one know what i could do to automatically kill off these processes. (1 Reply)
Discussion started by: namtab
1 Replies

3. Solaris

Any sys admins from uk?

Hello Guys, im new to this forum. Im from UK and ive recently completed my SCSA I & II and also got trained in Veritas Suite (Veritas Volume Manager and Veritas Clusters, Veritas NetBackup), SAN Configuration. I was trying to get a break as a junior sun solaris admin. I am applying for the jobs... (1 Reply)
Discussion started by: megadeth
1 Replies

4. UNIX for Dummies Questions & Answers

rouge process wiping files from a directory

I'm hoping you guys (the experts) can help me. We have a sweep directory (/opt/application/sweep) critical to our application process. The application will lay down a file in that directory, then about 15 seconds later a post process will come along and pick that file up and continue processing.... (2 Replies)
Discussion started by: hedrict
2 Replies

5. What is on Your Mind?

PEPSI MAX'S 2010 ADVERT.

What do you think about this Ad? O-XZk0yxCzc YouTube - PEPSI MAX'S 2010 FOOTBALL ADVERT FT AKON'S 'OH AFRICA' (FEATURE LENGTH) I can't stop watching it, it is entertaining... What is your best Advert. in 2010??? (0 Replies)
Discussion started by: malcomex999
0 Replies

6. What is on Your Mind?

Thank you members and admins

Got a raise and a formal position of 'unix system engineer' in 2016. I would like to thank you members and admins. This would not be possible without you. I will mention some.. Thank you Don, for making me learn and understand the importance of standards, which i try to apply as much as i... (3 Replies)
Discussion started by: Peasant
3 Replies
PBUILDER-DIST(1)					      General Commands Manual						  PBUILDER-DIST(1)

NAME
pbuilder-dist, cowbuilder-dist - multi-distribution pbuilder/cowbuilder wrapper SYNOPSIS
pbuilder-dist distribution [architecture] operation [options] [...] cowbuilder-dist distribution [architecture] operation [options] [...] DESCRIPTION
pbuilder-dist is a wrapper that makes it easy to use pbuilder with many different versions of Ubuntu and/or Debian. It is common to symlink this script in order to give it many names in the form of pbuilder-distribution or pbuilder-distribution-architec- ture, like for example pbuilder-feisty, pbuilder-sid, pbuilder-gutsy-i386, etc. The same applies to cowbuilder-dist, which uses cowbuilder. The main difference between both is that pbuilder compresses the created chroot as a a tarball, thus using less disc space but needing to uncompress (and possibly compress) its contents again on each run, and cowbuilder doesn't do this. USAGE
There are many arguments listed on the synopsis; each of them, if used, has to be used exactly in the same order as it appears there. In case you renamed the script to pbuilder-distribution, do not use the distribution parameter; same with i386 / amd64 if the name also con- tains -architecture. distribution Replace this with the codename of the version of Ubuntu or Debian you want to use. architecture This optional parameter will attempt to construct a chroot in a foreign architecture. For some architecture pairs (e.g. i386 on an amd64 install), the chroot will be created natively. For others (e.g. armel on an i386 install), qemu-user-static will be used. Note that some combinations (e.g. amd64 on an i386 install) require special separate kernel handling, and may break in unexpected ways. operation Replace this with the action you want pbuilder to do (create, update, build, clean, login or execute). If you don't specify any action, but the next argument is a .dsc file, it will assume that it should build. Check its manpage for more details. [...] Replace this with other parameters, if needed. For example, if build is the option, you will need to also specify a .dsc file. As a special feature, if you specify a .dsc file you can skip the build option and this script will automatically assume that building is the action you want to do. OPTIONS
--main-only (deprecated: mainonly) If you specify this option, only packages from the main (in Debian) or main and restricted (in Ubuntu) components will be used. By default, all official components are enabled. This only has effect when creating a new environment. --debug-echo The generated pbuilder/cowbuilder command will be printed to the standard output instead of being executed. This is useful for debugging. --buildresult DIRECTORY (pbuilder-dist only) If this option is specified, the resultant files of the pbuilder build are placed in DIRECTORY. --release-only Only use the release pocket. Default for development releases. --security-only Only use the release and security pockets. Suitable environment for preparing security updates. --updates-only Only use the release, security, and updates pocket. Not the proposed-updates pocket. EXAMPLES
pbuilder-dist gutsy create Creates a pbuilder environment for Ubuntu Gutsy, with all components enabled. pbuilder-sid --main-only create Creates a pbuilder environment for Debian Sid, with only the main component. pbuilder-feisty build ./sample_1.0-0ubuntu1.dsc Builds the specified package on an already existing Ubuntu Feisty environment. pbuilder-dist feisty withlog build ./sample_1.0-0ubuntu1.dsc Same as above, but stores pbuilder's output on a file. pbuilder-etch i386 update Updates an existing i386-architecture Debian Etch environment on an amd64 system. cowbuilder-experimental create Creates a cowbuilder environment for Debian Experimental. FILES AND ENVIRONMENT VARIABLES
By default, pbuilder-dist will store all the files it generates in ~/pbuilder/. This can be changed by setting the PBUILDFOLDER environment variable. If the directory doesn't exist, it will be created on the run. A file with the log of the last operation, called last_operation.log, will be saved in the results subdirectory of each build environment. The default authentication method is sudo. You can change this by setting the PBUILDAUTH variable. By default, pbuilder-dist use the master Debian and Ubuntu mirrors. The pbuilder MIRRORSITE and OTHERMIRROR variables are supported, as are the standard ubuntu-dev-tools variables: UBUNTUTOOLS_DEBIAN_MIRROR, PBUILDER_DIST_DEBIAN_MIRROR, UBUNTUTOOLS_DEBSEC_MIRROR, PBUILDER_DIST_DEBSEC_MIRROR, UBUNTUTOOLS_UBUNTU_MIRROR, PBUILDER_DIST_UBUNTU, UBUNTUTOOLS_UBUNTU_PORTS_MIRROR, and PBUILDER_DIST_UBUNTU_PORTS_MIRROR. See ubuntu-dev-tools (5) for details. You may also want to know that pbuilder-dist exports DIST and ARCH environment variables to the invoked process, containing the name of the distribution and the architecture targeted by the current build. You can make use of them, for example, in pbuilderrc. BUGS
If you experience any problem with this script contact me on rainct@ubuntu.com or file a bug at https://bugs.launch- pad.net/ubuntu/+source/ubuntu-dev-tools. Please ensure first that the problem is really this script and not an issue with pbuilder or cowbuilder themselves. SEE ALSO
pbuilder(1), pbuilderrc(5), cowbuilder(1), ubuntu-dev-tools(5). AUTHORS
pbuilder-dist and this manual page were written by Siegfried-A. Gevatter <rainct@ubuntu.com>, with contributions from Iain Lane <iain@orangesquash.org.uk>, Emmet Hikory <persia@ubuntu.com> and others. pbuilder-dist is released under the GNU General Public License, version 2 or later. ubuntu-dev-tools January 10, 2008 PBUILDER-DIST(1)
All times are GMT -4. The time now is 05:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy